This record as markdown: /tools/io-github-dave-london-github/poetry.md
What poetry does on Github
AI agents invoke poetry 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 poetry is rated High
This tool executes Poetry commands (a Python dependency/package manager) on the system. Since it runs arbitrary CLI commands, it can install/remove packages, modify project configuration, publish packages, run scripts, etc. The blast radius is high because an AI agent could use it to install malicious packages, exfiltrate data via published packages, or alter project dependencies in harmful ways.
From the tool's definition "Runs Poetry commands" — actively executes arbitrary Poetry CLI commands
Attacks that exploit this kind of access
The rule that runs poetry 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 poetry, this is the rule to start with:
poetry 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 poetry call is checked against it from then on.
Questions about poetry
Runs Poetry commands and returns structured output. 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 poetry: 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.
poetry 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 poetry 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 poetry. 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.
poetry 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