Get multiple markets by tickers and/or mint addresses (up to 100 results).
AI agents call get_markets_batch 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 market information from the Kalshi prediction market in batch form. It performs a data lookup operation with no side effects, state changes, or irreversible actions. The worst-case misuse would be information disclosure or excessive querying, which presents minimal risk. It falls squarely into the Read category.
From the tool's definition Tool name 'get_markets_batch' and description 'Get multiple markets by tickers and/or mint addresses (up to 100 results)' indicate a read-only query operation that retrieves market data without modifying, deleting, or executing any operations.
Documented attack patterns abuse exactly the kind of access get_markets_batch 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_markets_batch:
{
"version": "1",
"default": "deny",
"tools": {
"get_markets_batch": {}
}
}get_markets_batch 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 multiple markets by tickers and/or mint addresses (up to 100 results). 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_markets_batch: 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_markets_batch 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_markets_batch 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_markets_batch. 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_markets_batch 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.