Use this when you need to determine the outcome of a real-world event for prediction market settlement. Takes a natural language question (e.g. "Did BTC reach $100K?", "Did France win the 2026 World Cup?") and returns a structured resolution with confidence score. 1. question: the original questi...
Part of the Event Resolver API server.
Free to start. No card required.
AI agents use event_resolve_outcome to create or modify resources in Event Resolver API. Write operations carry medium risk because an autonomous agent could trigger bulk unintended modifications. Rate limits prevent a single agent session from making hundreds of changes in rapid succession. Argument validation ensures the agent passes expected values.
Without a policy, an AI agent could call event_resolve_outcome repeatedly, creating or modifying resources faster than any human could review. PolicyLayer's rate limiting ensures write operations happen at a controlled pace, and argument validation catches malformed or unexpected inputs before they reach Event Resolver API.
Write tools can modify data. A rate limit prevents runaway bulk operations from AI agents.
{
"version": "1",
"default": "deny",
"tools": {
"event_resolve_outcome": {
"limits": [
{
"counter": "event_resolve_outcome_rate",
"window": "minute",
"max": 30,
"scope": "grant"
}
]
}
}
}See the full Event Resolver API policy for all 3 tools.
These attack patterns abuse exactly the kind of access event_resolve_outcome gives an agent. Each links to the full case and the policy that stops it:
Other write tools across the catalogue. The same approach applies to each: rate-limit and validate the arguments.
Use this when you need to determine the outcome of a real-world event for prediction market settlement. Takes a natural language question (e.g. "Did BTC reach $100K?", "Did France win the 2026 World Cup?") and returns a structured resolution with confidence score. 1. question: the original question being resolved 2. resolved: whether the event can be conclusively determined (true/false) 3. outcome: the determined result -- "Yes"/"No" for binary, a number for numeric, or a category string 4. confidence: 0-100 score indicating certainty of the resolution 5. sources: array of data sources consulted, each with name, url, and whether it agrees with the outcome 6. timestamp: ISO timestamp of when the resolution was performed Example output: { "question": "Did BTC reach $100K?", "resolved": true, "outcome": "Yes", "confidence": 95, "sources": [{ "name": "CoinGecko", "url": "https://coingecko.com", "agrees": true }], "timestamp": "2026-04-13T12:00:00Z" } Use this when settling prediction market contracts, verifying event outcomes for on-chain resolution, or building automated settlement oracles. Handles price-based questions via CoinGecko and general questions via web search aggregation. Do NOT use for prediction market odds -- use prediction_list_markets instead. Do NOT use for crypto prices only -- use token_get_price instead. Do NOT use for full fact checking with sources -- use research_check_fact instead. Do NOT use for trust/security scoring -- use trust_score_evaluate instead.. It is categorised as a Write tool in the Event Resolver API MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Event Resolver API MCP server in PolicyLayer and add a rule for event_resolve_outcome: 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 Event Resolver API. Nothing to install.
event_resolve_outcome is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.
Yes. Add a rate_limit block to the event_resolve_outcome 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 event_resolve_outcome. 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.
event_resolve_outcome is provided by the Event Resolver API MCP server (https://event-resolver.api.klymax402.com/mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Deterministic rules across all 3 Event Resolver API tools. Per-identity grants. Full audit log. Live in minutes. Nothing to install.
Free to start. No card required.
4,600+ MCP servers and 31,000+ tools scanned and risk-classified.