Get details of a Pipe Endpoint in the Tinybird Workspace, such as the nodes SQLs to understand what they do or what Data Sources they use
AI agents call get-pipe 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 read-only operations that query and return metadata about existing Pipe Endpoints and their configuration. It does not modify, delete, or execute any data operations. The blast radius of misuse is minimal since it only exposes information about workflow structure and data source dependencies.
From the tool's definition Tool retrieves 'details of a Pipe Endpoint' including 'nodes SQLs' and 'Data Sources they use' — purely informational queries with no side effects.
Documented attack patterns abuse exactly the kind of access get-pipe 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 get-pipe:
{
"version": "1",
"default": "deny",
"tools": {
"get-pipe": {}
}
}get-pipe 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.
Get details of a Pipe Endpoint in the Tinybird Workspace, such as the nodes SQLs to understand what they do or what Data Sources they use. 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 get-pipe: 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.
get-pipe 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 get-pipe 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 get-pipe. 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.
get-pipe 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.