List relay pipelines.
AI agents call list_relay_pipelines to retrieve information from Agent Runtime without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves and displays information about relay pipelines. It performs no create, update, delete, or execute operations. The blast radius of misuse is minimal—an agent listing pipelines gains observability into system state but cannot modify or damage any infrastructure or data. This is a straightforward Read category tool.
From the tool's definition Tool name 'list_relay_pipelines' and description 'List relay pipelines' indicate a query/retrieval operation with no side effects. The verb 'list' is a classic read-only action that retrieves existing data without modification.
Attacks that exploit this kind of access
List relay pipelines. It is categorised as a Read tool in the Agent Runtime MCP Server, which means it retrieves data without modifying state.
Register the Agent Runtime MCP server in PolicyLayer and add a rule for list_relay_pipelines: 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 Agent Runtime. Nothing to install.
list_relay_pipelines is a Read tool with low risk. Read-only tools are generally safe to allow by default.
Yes. Add a rate_limit block to the list_relay_pipelines 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 list_relay_pipelines. 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.
list_relay_pipelines is provided by the Agent Runtime MCP server (marc-shade/agent-runtime-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 →