Requests data from a Pipe Endpoint in the Tinybird Workspace, includes parameters
AI agents call request-pipe-data 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 retrieves or queries data from a Tinybird Pipe without creating, modifying, or deleting any data. It is a read-only operation analogous to fetching results from an API endpoint. The low severity reflects minimal blast radius—misuse would at worst retrieve unintended data, not cause destructive or financial harm.
From the tool's definition Tool requests data from a Pipe Endpoint with parameters. The name 'request-pipe-data' and description 'Requests data from a Pipe' indicate a data retrieval operation with no modification or deletion capability.
Documented attack patterns abuse exactly the kind of access request-pipe-data 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 request-pipe-data:
{
"version": "1",
"default": "deny",
"tools": {
"request-pipe-data": {}
}
}request-pipe-data 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.
Requests data from a Pipe Endpoint in the Tinybird Workspace, includes parameters. 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 request-pipe-data: 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.
request-pipe-data 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 request-pipe-data 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 request-pipe-data. 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.
request-pipe-data 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.