Read a file from the local Onboarded repository. Requires onboardedRepoPath to be configured.
AI agents call repo_read to retrieve information from Onboarded 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 contents from a local repository without modifying, executing, or deleting anything. It is a straightforward read operation with minimal blast radius—the worst outcome would be unauthorized information disclosure if access controls are weak, but the tool itself performs no destructive or executable actions.
From the tool's definition Tool name is 'repo_read' and description explicitly states 'Read a file from the local Onboarded repository.' The verb 'Read' and lack of modification language clearly indicate data retrieval with no side effects.
Attacks that exploit this kind of access
Read a file from the local Onboarded repository. Requires onboardedRepoPath to be configured. It is categorised as a Read tool in the Onboarded MCP Server MCP Server, which means it retrieves data without modifying state.
Register the Onboarded MCP Server MCP server in PolicyLayer and add a rule for repo_read: 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 Onboarded MCP Server. Nothing to install.
repo_read 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 repo_read 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 repo_read. 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.
repo_read is provided by the Onboarded MCP Server MCP server (onboardedinc/onboarded-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 →