AI agents call get-context to retrieve information from Doc Lib without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This is a straightforward read operation that queries and returns documentation chunks based on semantic search. No data is created, modified, deleted, or executed. The blast radius is minimal—the worst an AI agent could do is retrieve irrelevant documentation, which causes no harm.
From the tool's definition Tool retrieves documentation and provides context; 'Retrieves relevant documentation' indicates data retrieval with no modification or side effects. Filtering/boosting are read-only operations.
Attacks that exploit this kind of access
Retrieves relevant documentation to provide Cline with context for project tasks. Optionally filter or boost by tags. It is categorised as a Read tool in the Doc Lib MCP Server, which means it retrieves data without modifying state.
Register the Doc Lib MCP server in PolicyLayer and add a rule for get-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 Doc Lib. Nothing to install.
get-context is a Read tool with low risk. Read-only tools are generally safe to allow by default.
Yes. Add a rate_limit block to the get-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 get-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.
get-context is provided by the Doc Lib MCP server (shifusen329/doc-lib-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 →