tool_with_context
AI agents use tool_with_context to create or update resources in API Docs MCP Server — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your API Docs MCP Server environment.
An AI agent can call tool_with_context faster than any human can review — one bad instruction and it creates or modifies resources in API Docs MCP Server by the hundred, each call as confident as the last.
Attacks that exploit this kind of access
tool_with_context. It is categorised as a Write tool in the API Docs MCP Server MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the API Docs MCP Server MCP server in PolicyLayer and add a rule for tool_with_context: allow, deny, rate-limit, or require approval. Point your MCP client at the PolicyLayer proxy URL and the rule is enforced on every call, before it reaches API Docs MCP Server. Nothing to install.
tool_with_context is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.
Yes. Add a rate_limit block to the tool_with_context rule in your PolicyLayer policy. For example, setting max: 10 and window: 60 limits the tool to 10 calls per minute. Rate limits are tracked per agent session and reset automatically.
Set action: deny in the PolicyLayer policy for tool_with_context. The AI agent will receive a policy violation error and cannot call the tool. You can also include a reason field to explain why the tool is blocked.
tool_with_context is provided by the API Docs MCP Server MCP server (shotanagafuchi/api-docs-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Every MCP server has a record like this.
Type a name, get the same breakdown: verified identity, auth posture, risk grade, capabilities, recommended policy.
Teams ship this data inside their own products. See what a licence covers →