generate_badges
AI agents use generate_badges to create or update resources in Pypi:pypreset — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Pypi:pypreset environment.
The tool likely generates badge markdown/images and writes them to project documentation files (README, etc.), which is a reversible write operation. Without explicit description, confidence is moderate. Severity is medium because unintended badge generation could clutter documentation but is easily reversed.
From the tool's definition Tool name 'generate_badges' and context of a Python project scaffolding server suggest file creation/modification. Description is empty, limiting certainty. Sibling tools like 'create_project' and 'augment_project' indicate this server modifies project files.
Attacks that exploit this kind of access
generate_badges. It is categorised as a Write tool in the Pypi:pypreset MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Pypi:pypreset MCP server in PolicyLayer and add a rule for generate_badges: 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 Pypi:pypreset. Nothing to install.
generate_badges is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.
Yes. Add a rate_limit block to the generate_badges 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 generate_badges. 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.
generate_badges is provided by the Pypi:pypreset MCP server (KaiErikNiermann/pypreset). 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 →