Fetch the README of a GitHub repository using owner/name format.
AI agents call get_repository_readme to retrieve information from Repo Radar MCP without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves and returns publicly available README documentation from a GitHub repository. It performs no write, delete, execute, or financial operations. The only potential risk is information disclosure of public content, which carries minimal security impact. Confidence is high because the description is clear and explicit about fetching (read-only) a standard repository artifact.
From the tool's definition Tool description states 'Fetch the README of a GitHub repository' — a retrieval operation with no modification or execution. README files are public documentation.
Attacks that exploit this kind of access
Fetch the README of a GitHub repository using owner/name format. It is categorised as a Read tool in the Repo Radar MCP MCP Server, which means it retrieves data without modifying state.
Register the Repo Radar MCP server in PolicyLayer and add a rule for get_repository_readme: 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 Repo Radar MCP. Nothing to install.
get_repository_readme 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_repository_readme 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_repository_readme. 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_repository_readme is provided by the Repo Radar MCP server (javiermorron/repo-radar-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 →