AI agents invoke run_pipeline to trigger actions in Tenzir MCP Server. 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.
Pipelines in cybersecurity contexts typically execute transformations, queries, and analyses on sensitive data. While the description is empty, the server context and tool name strongly suggest this executes user-defined or pre-configured data processing workflows whose effects depend on pipeline configuration and data arguments.
From the tool's definition Tool named 'run_pipeline' on a server that 'Enables AI assistants to interact with security data pipelines' and 'process[es] and analyz[es] cybersecurity data'.
Documented attack patterns abuse exactly the kind of access run_pipeline gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Tenzir MCP Server, and nothing reaches the server without passing your rules. This is the rule we recommend for run_pipeline:
{
"version": "1",
"default": "deny",
"tools": {
"run_pipeline": {
"limits": [
{
"counter": "run_pipeline_rate",
"window": "minute",
"max": 10,
"scope": "grant"
}
]
}
}
}run_pipeline 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.
Free to start. No card required.
run_pipeline. It is categorised as a Execute tool in the Tenzir MCP Server MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
Register the Tenzir MCP Server MCP server in PolicyLayer and add a rule for run_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 Tenzir MCP Server. Nothing to install.
run_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 run_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 run_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.
run_pipeline is provided by the Tenzir MCP Server MCP server (tenzir/mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from Tenzir MCP Server, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.
Free to start. No card required.
15 Tenzir MCP Server tools catalogued and risk-classified — across an index of 43,000+ MCP servers.