Get conditions (markets that have been prepared on-chain) with resolution status. Useful for finding resolved/unresolved markets.
AI agents call get_conditions to retrieve information from Limitless MCP without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves market condition data and their resolution status from on-chain sources. It is purely informational with no side effects—no data is created, modified, deleted, or used to execute external operations. The low severity reflects minimal risk even in an adversarial scenario, as querying read-only market metadata poses no direct harm.
From the tool's definition Tool name 'get_conditions' and description 'Get conditions (markets that have been prepared on-chain) with resolution status' indicates a query operation that retrieves on-chain data without modification.
Attacks that exploit this kind of access
Get conditions (markets that have been prepared on-chain) with resolution status. Useful for finding resolved/unresolved markets. It is categorised as a Read tool in the Limitless MCP MCP Server, which means it retrieves data without modifying state.
Register the Limitless MCP server in PolicyLayer and add a rule for get_conditions: 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 Limitless MCP. Nothing to install.
get_conditions 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_conditions 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_conditions. 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_conditions is provided by the Limitless MCP server (paulieb14/limitless-subgraphs). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Every MCP server has a record like this.
Type a name, get the same breakdown: verified identity, auth posture, risk grade, capabilities, recommended policy.
Teams ship this data inside their own products. See what a licence covers →