Reads the content of a specified file and retrieves its metadata.
AI agents call read-file-with-metadata to retrieve information from Codebase MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves file content and metadata without creating, modifying, deleting, or executing anything. It is a pure read operation. Severity is low because reading files in a codebase analysis context presents minimal risk—the tool operates within a 'restricted root directory' and has no side effects.
From the tool's definition Tool name is 'read-file-with-metadata' and description states 'Reads the content of a specified file and retrieves its metadata.' The verb 'Reads' and 'retrieves' indicate data querying with no modification or execution.
Attacks that exploit this kind of access
Reads the content of a specified file and retrieves its metadata. It is categorised as a Read tool in the Codebase MCP Server MCP Server, which means it retrieves data without modifying state.
Register the Codebase MCP Server MCP server in PolicyLayer and add a rule for read-file-with-metadata: 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 Codebase MCP Server. Nothing to install.
read-file-with-metadata 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 read-file-with-metadata 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 read-file-with-metadata. 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.
read-file-with-metadata is provided by the Codebase MCP Server MCP server (myunghobae/codebase-mcp-server). 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 →