Execute a pipeline by ID or name using the AFC PipelineEngine
AI agents invoke afc-execute-pipeline to trigger actions in AFC Commander (Free Edition). 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 triggers execution of pre-defined command pipelines, which can run arbitrary CLI commands registered in the registry. The blast radius depends on what commands are stored in those pipelines—they could perform destructive operations, financial transactions, or modify systems.
From the tool's definition The tool description states it will "Execute a pipeline by ID or name using the AFC PipelineEngine". The word 'execute' combined with pipelines (which are sequences of registered CLI commands) indicates this tool runs external operations whose effects depend…
Attacks that exploit this kind of access
Execute a pipeline by ID or name using the AFC PipelineEngine. It is categorised as a Execute tool in the AFC Commander (Free Edition) MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
Register the AFC Commander (Free Edition) MCP server in PolicyLayer and add a rule for afc-execute-pipeline: 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 AFC Commander (Free Edition). Nothing to install.
afc-execute-pipeline 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 afc-execute-pipeline 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 afc-execute-pipeline. 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.
afc-execute-pipeline is provided by the AFC Commander (Free Edition) MCP server (trace186/afc-commander-cli-registry-with-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 →