This record as markdown: /tools/io-github-dave-london-github/info.md
What info does on Github
AI agents call info to retrieve information from Github without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
Why info is rated Low
The incomplete description ('Runs') provides limited certainty, but the tool name 'info' and its position in a GitHub operations server strongly suggest a read-only retrieval function. If this tool executes arbitrary code or commands, it would escalate to Execute category; however, without that evidence, the most likely classification is Read. Confidence is reduced due to truncated description.
From the tool's definition Tool name is 'info' and description begins 'Runs' (incomplete). Based on the naming pattern and context as a GitHub MCP server, 'info' typically retrieves information about GitHub resources.
Attacks that exploit this kind of access
The rule that runs info safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Github, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For info, this is the rule to start with:
info is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.
The button opens the PolicyLayer dashboard: create your workspace, connect Github, apply this rule, and every info call is checked against it from then on.
Questions about info
Runs. It is categorised as a Read tool in the Github MCP Server, which means it retrieves data without modifying state.
Register the Github MCP server in PolicyLayer and add a rule for info: 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 Github. Nothing to install.
info 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 info 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 info. 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.
info is provided by the Github MCP server (@paretools/github). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Github, and thousands of servers like it.
This server
Across the catalogue