Fetch metadata for a pull request (ids, SHAs, author).
AI agents call github_pr_get to retrieve information from Promethean OS MCP without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves information about pull requests without modifying, deleting, or executing code. It is a passive data retrieval operation. The metadata it returns (pull request IDs, commit SHAs, and author information) are typically public or at least readable information in most GitHub repositories. There is no capability to modify repositories, execute workflows, or trigger actions.
From the tool's definition The tool description states it 'Fetch[es] metadata for a pull request (ids, SHAs, author)'. The verb 'fetch' and the focus on retrieving non-sensitive metadata indicates a read-only operation with no side effects.
Attacks that exploit this kind of access
Fetch metadata for a pull request (ids, SHAs, author). It is categorised as a Read tool in the Promethean OS MCP MCP Server, which means it retrieves data without modifying state.
Register the Promethean OS MCP server in PolicyLayer and add a rule for github_pr_get: 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 Promethean OS MCP. Nothing to install.
github_pr_get 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 github_pr_get 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 github_pr_get. 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.
github_pr_get is provided by the Promethean OS MCP server (octave-commons/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 →