Send a prompt to the local Augment coding agent
AI agents invoke run_augment_prompt to trigger actions in AI Development Pipeline MCP. 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.
This tool invokes an external coding agent (Augment) with user-supplied prompts. The agent can generate, modify, or execute code based on the prompt content. While the tool itself doesn't directly delete or move money, it triggers code generation and modification actions whose consequences are argument-dependent and potentially uncontrolled.
From the tool's definition The tool 'run_augment_prompt' sends a prompt to the Augment coding agent, which is described as a 'development tool' capable of code generation and modification.
Attacks that exploit this kind of access
Send a prompt to the local Augment coding agent. It is categorised as a Execute tool in the AI Development Pipeline MCP MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
Register the AI Development Pipeline MCP server in PolicyLayer and add a rule for run_augment_prompt: 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 AI Development Pipeline MCP. Nothing to install.
run_augment_prompt 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 run_augment_prompt 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 run_augment_prompt. 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.
run_augment_prompt is provided by the AI Development Pipeline MCP server (theburgerllc/ai-development-pipeline-mcp). 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 →