Return the full contents of a local documentation file.
AI agents call get_local_content_tool to retrieve information from Simple MCP Tool Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves and queries local documentation content without side effects. It is a read operation that does not create, modify, delete, or execute anything. The low severity reflects minimal blast radius—an AI agent using this tool would only be able to access existing documentation, with no capability to alter system state or trigger external operations.
From the tool's definition Tool name contains 'get' and description states 'Return the full contents' with no mention of modification, deletion, or execution. It retrieves data from local documentation files.
Attacks that exploit this kind of access
Return the full contents of a local documentation file. It is categorised as a Read tool in the Simple MCP Tool Server MCP Server, which means it retrieves data without modifying state.
Register the Simple MCP Tool Server MCP server in PolicyLayer and add a rule for get_local_content_tool: 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 Simple MCP Tool Server. Nothing to install.
get_local_content_tool 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_local_content_tool 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_local_content_tool. 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_local_content_tool is provided by the Simple MCP Tool Server MCP server (slawekradzyminski/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 →