Get a single event by ticker. Returns event metadata including series ticker, subtitle, markets, strike information and volume.
AI agents call get_event 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 is a straightforward read operation that retrieves event information from the Kalshi prediction market. It queries and returns metadata without creating, modifying, deleting, or executing any operations. The tool has minimal blast radius as it only exposes public market data.
From the tool's definition Tool name 'get_event' and description 'Get a single event by ticker. Returns event metadata' indicate data retrieval with no modification or side effects. The returned data (metadata, markets, strike information, volume) are read-only queries.
Documented attack patterns abuse exactly the kind of access get_event 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_event:
{
"version": "1",
"default": "deny",
"tools": {
"get_event": {}
}
}get_event 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 a single event by ticker. Returns event metadata including series ticker, subtitle, markets, strike information and volume. 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_event: 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_event 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_event 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_event. 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_event 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.