Run a Yeoman generator
AI agents invoke yeoman_generate to trigger actions in Mcp Yeoman. 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.
Running a Yeoman generator executes arbitrary code and scripts on the host system, creates and potentially overwrites files, and may install packages. This is an Execute-category action with high severity because a misused generator could scaffold malicious code, overwrite existing project files, or execute post-install hooks with unintended effects.
From the tool's definition "Run a Yeoman generator" — executes a Yeoman generator programmatically, which can create files, modify the filesystem, install dependencies, and trigger arbitrary scaffolding scripts.
Attacks that exploit this kind of access
Run a Yeoman generator. It is categorised as a Execute tool in the Mcp Yeoman MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
Register the Mcp Yeoman MCP server in PolicyLayer and add a rule for yeoman_generate: 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 Mcp Yeoman. Nothing to install.
yeoman_generate 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 yeoman_generate 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 yeoman_generate. 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.
yeoman_generate is provided by the Mcp Yeoman MCP server (thirdstrandstudio/mcp-yeoman). 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 →