Low Risk

get_markets

Get a paginated list of markets with optional filtering.

How to control get_markets ↓

What get_markets does on DFlow MCP Server

AI agents call get_markets 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.

Low Risk

Why get_markets needs a policy

This tool retrieves market data from the Kalshi prediction market exchange. It performs a read-only query with optional filtering parameters and returns paginated results. There are no side effects, no financial transactions, no code execution, and no data modification. This is a straightforward data retrieval operation, making it clearly a Read category tool with low severity risk.

From the tool's definition Tool name 'get_markets' and description 'Get a paginated list of markets with optional filtering' indicate a retrieval operation that queries data without modifying or executing any operations.

Documented attack patterns abuse exactly the kind of access get_markets gives an agent:

How to control get_markets

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:

policy.json
{
  "version": "1",
  "default": "deny",
  "tools": {
    "get_markets": {}
  }
}

get_markets is read-only, so it stays allowed — but everything else on the server is denied unless you say otherwise.

  1. Create a free account and register DFlow MCP Server — nothing to install.
  2. Add this policy — paste it, or build it visually.
  3. Point your MCP client (Claude, Cursor, anything) at your gateway URL.
CAP THIS TOOL →

Free to start. No card required.

Related tools and policies

Go deeper

Questions about get_markets

What does the get_markets tool do? +

Get a paginated list of markets with optional filtering. It is categorised as a Read tool in the DFlow MCP Server MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on get_markets? +

Register the DFlow MCP Server MCP server in PolicyLayer and add a rule for get_markets: 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.

What risk level is get_markets? +

get_markets is a Read tool with low risk. Read-only tools are generally safe to allow by default.

Can I rate-limit get_markets? +

Yes. Add a rate_limit block to the get_markets 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.

How do I block get_markets completely? +

Set action: deny in the PolicyLayer policy for get_markets. 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.

What MCP server provides get_markets? +

get_markets 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.

Enforce policy on every DFlow MCP Server tool call.

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.

// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.