Overview of the question.market MCP server: available tools, onboarding flow, and links.
AI agents call question_market to retrieve information from Question Market without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This is a documentation/info tool that lists available capabilities and onboarding guidance. It retrieves and presents metadata about the server itself without modifying state, executing transactions, or triggering financial operations. The sibling tools (buy_shares, claim_winnings, create_market) handle actual trading and market actions; this tool simply describes them.
From the tool's definition Tool described as providing 'Overview' of the MCP server, 'available tools, onboarding flow, and links' — purely informational retrieval with no data modification or external execution.
Attacks that exploit this kind of access
Overview of the question.market MCP server: available tools, onboarding flow, and links. It is categorised as a Read tool in the Question Market MCP Server, which means it retrieves data without modifying state.
Register the Question Market MCP server in PolicyLayer and add a rule for question_market: 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 Question Market. Nothing to install.
question_market 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 question_market 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 question_market. 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.
question_market is provided by the Question Market MCP server (qmrkt/mcp-server). 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 →