Get detailed information about a specific Tailpipe partition, including its configuration and statistics.
AI agents call tailpipe_partition_show to retrieve information from Tailpipe without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
The tool retrieves and displays information about an existing partition. It performs a query operation (show/get) that returns read-only data about configuration and statistics. There is no indication of data modification, deletion, code execution, or financial operations. This is a classic Read operation with minimal blast radius.
From the tool's definition Tool name contains 'show' and description explicitly states 'Get detailed information about a specific Tailpipe partition, including its configuration and statistics.' These are retrieval operations with no modification or side effects.
Documented attack patterns abuse exactly the kind of access tailpipe_partition_show gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Tailpipe, and nothing reaches the server without passing your rules. This is the rule we recommend for tailpipe_partition_show:
{
"version": "1",
"default": "deny",
"tools": {
"tailpipe_partition_show": {}
}
} tailpipe_partition_show 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 detailed information about a specific Tailpipe partition, including its configuration and statistics. It is categorised as a Read tool in the Tailpipe MCP Server, which means it retrieves data without modifying state.
Register the Tailpipe MCP server in PolicyLayer and add a rule for tailpipe_partition_show: 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 Tailpipe. Nothing to install.
tailpipe_partition_show 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 tailpipe_partition_show 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 tailpipe_partition_show. 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.
tailpipe_partition_show is provided by the Tailpipe MCP server (turbot/tailpipe-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from Tailpipe, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.
Free to start. No card required.
10 Tailpipe tools catalogued and risk-classified — across an index of 43,000+ MCP servers.