AI agents call get_code_structure to retrieve information from MCP File Edit without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool queries and returns information about code organization (likely AST or outline data) without modifying, executing, or deleting any files. It is a pure read operation with no side effects, making it the least risky category. Low severity because exposure of code structure metadata poses minimal risk even if misused by an AI agent.
From the tool's definition Tool name 'get_code_structure' and description 'Get the overall code structure of a file' indicate read-only retrieval of structural metadata about code.
Documented attack patterns abuse exactly the kind of access get_code_structure gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and MCP File Edit, and nothing reaches the server without passing your rules. This is the rule we recommend for get_code_structure:
{
"version": "1",
"default": "deny",
"tools": {
"get_code_structure": {}
}
}get_code_structure is read-only, so it stays allowed — but everything else on the server is denied unless you say otherwise.
Free to start. No card required.
Get the overall code structure of a file. It is categorised as a Read tool in the MCP File Edit MCP Server, which means it retrieves data without modifying state.
Register the MCP File Edit MCP server in PolicyLayer and add a rule for get_code_structure: 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 MCP File Edit. Nothing to install.
get_code_structure 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_code_structure 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_code_structure. 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_code_structure is provided by the MCP File Edit MCP server (patrickomatik/mcp-file-edit). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from MCP File Edit, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.
Free to start. No card required.
32 MCP File Edit tools catalogued and risk-classified — across an index of 43,000+ MCP servers.