Push a .datasource or .pipe file to the Workspace
AI agents use push-datafile to create or update resources in Tinybird MCP server — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Tinybird MCP server environment.
The tool allows uploading configuration files (.datasource or .pipe) to modify the Workspace structure. This is a write operation that creates or updates resources but is reversible (files can be overwritten or deleted). It does not execute arbitrary code, delete data permanently, or move money.
From the tool's definition Tool name and description indicate it 'Push a .datasource or .pipe file to the Workspace' — this creates or modifies data source and pipe definitions in the Workspace, which is a reversible write operation.
Documented attack patterns abuse exactly the kind of access push-datafile 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 push-datafile:
{
"version": "1",
"default": "deny",
"tools": {
"push-datafile": {
"limits": [
{
"counter": "push-datafile_rate",
"window": "minute",
"max": 30,
"scope": "grant"
}
]
}
}
}push-datafile stays usable, but capped — an agent stuck in a loop can't make hundreds of changes a minute. Everything else on the server is denied unless you say otherwise.
Free to start. No card required.
Push a .datasource or .pipe file to the Workspace. It is categorised as a Write tool in the Tinybird MCP server MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Tinybird MCP server MCP server in PolicyLayer and add a rule for push-datafile: 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.
push-datafile is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.
Yes. Add a rate_limit block to the push-datafile 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 push-datafile. 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.
push-datafile 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.