Assumptions
- You control which MCP servers are available to each workflow or environment.
- You can review tool capabilities before a server becomes available in production.
- Anthale can evaluate content that enters or leaves the workflow around MCP tool use.
Secure the integration
1
Inventory each server and its capabilities
Separate read-only lookup servers from servers that can change state, contact external systems, or expose sensitive
data. Do not treat every MCP server as the same risk tier.
2
Treat descriptors and tool output as untrusted inputs
Server metadata, tool descriptions, and tool responses can all influence model behavior. Evaluate the next boundary
before that content is trusted or reused.
3
Scope servers to the workflow that needs them
Give each workflow access only to the MCP servers and tools it needs. A read-only documentation assistant should not
inherit the same server set as a workflow that can change production state.
4
Gate sensitive actions with validation and approval
If an MCP tool can send data, write records, run code, or trigger an external effect, keep allowlists, argument
validation, and approval controls outside the model.
5
Log server, tool, and approval context
Record which server answered, which tool was proposed or called, what the approval decision was, and which policy
governed the content path.
6
Review descriptor or capability changes
A server that was safe last week can become risky when its tool set or descriptions change. Treat those changes as a
control review event, not as a routine prompt update.
What this looks like in code
Common failure patterns
- All MCP servers are exposed to every workflow by default.
- Tool descriptions are trusted as if they were developer-owned instructions.
- Sensitive MCP actions have no approval path because the client treats them as ordinary tool calls.
- Teams log the tool result but not the server identity or capability set that produced it.
Apply this in Anthale
- Create a first policy when you want to test an MCP boundary with a working Anthale policy.
- See the enforcement API when you need the exact contract for evaluating MCP content at runtime.
- Request access when you want help reviewing a live MCP workflow.