Low Risk

get_outcome_mints

Get a flat list of yes and no outcome mint pubkeys.

How to control get_outcome_mints ↓

What get_outcome_mints does on DFlow MCP Server

AI agents call get_outcome_mints 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_outcome_mints needs a policy

This tool retrieves outcome mint public keys from the Kalshi prediction market without modifying, executing, or deleting any data. It is a straightforward data query operation consistent with the Read category. The severity is low because retrieving public keys from a market data endpoint poses minimal risk even if misused by an AI agent.

From the tool's definition Tool description states 'Get a flat list of yes and no outcome mint pubkeys' - a retrieval operation with no side effects. The action verb 'Get' and the passive data retrieval nature indicate a read-only query.

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

How to control get_outcome_mints

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_outcome_mints:

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

get_outcome_mints 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_outcome_mints

What does the get_outcome_mints tool do? +

Get a flat list of yes and no outcome mint pubkeys. 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_outcome_mints? +

Register the DFlow MCP Server MCP server in PolicyLayer and add a rule for get_outcome_mints: 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_outcome_mints? +

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

Can I rate-limit get_outcome_mints? +

Yes. Add a rate_limit block to the get_outcome_mints 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_outcome_mints completely? +

Set action: deny in the PolicyLayer policy for get_outcome_mints. 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_outcome_mints? +

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