This record as markdown: /tools/io-github-dave-london-github/outdated.md
What outdated does on Github
AI agents invoke outdated to trigger actions in Github. What it does depends on the arguments the agent supplies, and its effects often reach beyond the immediate call: builds kicked off, notifications sent, workflows started.
Why outdated is rated High
The description is truncated to just 'Runs', which implies command execution. In the context of a GitHub/package management server with sibling tools like 'add-package', 'bazel', 'ansible-playbook', 'outdated' most likely runs a check for outdated dependencies (e.g., npm outdated, pip list --outdated). This is an Execute category action as it runs an external command.
From the tool's definition Tool name 'outdated' and description 'Runs' (truncated/uninformative) on a GitHub MCP server suggest it executes a command to check for outdated dependencies or packages
Attacks that exploit this kind of access
The rule that runs outdated 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 outdated, this is the rule to start with:
outdated stays usable, but rate-capped: a runaway agent can't fire it dozens of times a minute. 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 outdated call is checked against it from then on.
Questions about outdated
Runs. It is categorised as a Execute tool in the Github MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
Register the Github MCP server in PolicyLayer and add a rule for outdated: 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.
outdated is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.
Yes. Add a rate_limit block to the outdated 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 outdated. 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.
outdated 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.
Across the catalogue