AI agents call list-pipes to retrieve information from Tinybird MCP server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool performs a query/enumeration action that retrieves metadata about pipe endpoints in the workspace. It has no side effects, does not execute code, does not modify or delete data, and does not involve financial operations. It is a straightforward informational read operation with minimal blast radius if misused by an AI agent.
From the tool's definition Tool name and description indicate a list operation: 'List all Pipe Endpoints' retrieves and enumerates existing pipes without modification or deletion.
Documented attack patterns abuse exactly the kind of access list-pipes gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Tinybird MCP server, and nothing reaches the server without passing your rules. This is the rule we recommend for list-pipes:
{
"version": "1",
"default": "deny",
"tools": {
"list-pipes": {}
}
}list-pipes is read-only, so it stays allowed — but everything else on the server is denied unless you say otherwise.
Free to start. No card required.
List all Pipe Endpoints in the Tinybird Workspace. It is categorised as a Read tool in the Tinybird MCP server MCP Server, which means it retrieves data without modifying state.
Register the Tinybird MCP server MCP server in PolicyLayer and add a rule for list-pipes: 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 Tinybird MCP server. Nothing to install.
list-pipes 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-pipes 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-pipes. 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-pipes is provided by the Tinybird MCP server MCP server (tinybirdco/mcp-tinybird). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Deterministic rules across all 11 Tinybird MCP server tools. Per-identity grants. Full audit log. Live in minutes. Nothing to install.
Free to start. No card required.
11 Tinybird MCP server tools catalogued and risk-classified — across an index of 42,500+ MCP servers.