List available trackers with their context types and status
AI agents call list_trackers to retrieve information from ChurnFlow MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool queries and returns information about available trackers without creating, modifying, executing, or deleting any data. It is a straightforward read operation that provides visibility into the system's current state. Low severity because misuse would only expose tracker metadata, not cause harm or enable further attacks.
From the tool's definition Tool name 'list_trackers' and description 'List available trackers with their context types and status' indicate a retrieval operation with no modification or execution of side effects.
Documented attack patterns abuse exactly the kind of access list_trackers gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and ChurnFlow MCP Server, and nothing reaches the server without passing your rules. This is the rule we recommend for list_trackers:
{
"version": "1",
"default": "deny",
"tools": {
"list_trackers": {}
}
}list_trackers 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 available trackers with their context types and status. It is categorised as a Read tool in the ChurnFlow MCP Server MCP Server, which means it retrieves data without modifying state.
Register the ChurnFlow MCP Server MCP server in PolicyLayer and add a rule for list_trackers: 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 ChurnFlow MCP Server. Nothing to install.
list_trackers 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_trackers 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_trackers. 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_trackers is provided by the ChurnFlow MCP Server MCP server (jgsteeler/churnflow-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from ChurnFlow MCP Server, 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.
3 ChurnFlow MCP Server tools catalogued and risk-classified — across an index of 43,000+ MCP servers.