Get filtering options for each sport including scopes and competitions.
AI agents call get_filters_by_sports to retrieve information from DFlow 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 structured filter metadata for sports categories on the Kalshi prediction market. It performs a straightforward data query with no side effects, no execution of arbitrary operations, and no financial impact. The 'get' prefix and passive language ('Get filtering options') confirm read-only semantics.
From the tool's definition Tool name 'get_filters_by_sports' and description 'Get filtering options for each sport including scopes and competitions' indicate a retrieval operation that queries available filter metadata without modifying, executing, or affecting financial transactions.
Documented attack patterns abuse exactly the kind of access get_filters_by_sports gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and DFlow MCP Server, and nothing reaches the server without passing your rules. This is the rule we recommend for get_filters_by_sports:
{
"version": "1",
"default": "deny",
"tools": {
"get_filters_by_sports": {}
}
} get_filters_by_sports 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 filtering options for each sport including scopes and competitions. It is categorised as a Read tool in the DFlow MCP Server MCP Server, which means it retrieves data without modifying state.
Register the DFlow MCP Server MCP server in PolicyLayer and add a rule for get_filters_by_sports: 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 DFlow MCP Server. Nothing to install.
get_filters_by_sports 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_filters_by_sports 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_filters_by_sports. 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_filters_by_sports is provided by the DFlow MCP Server MCP server (opensvm/dflow-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from DFlow 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.
24 DFlow MCP Server tools catalogued and risk-classified — across an index of 43,000+ MCP servers.