AI agents call research.signal.what_if to retrieve information from Rekko MCP without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
Despite the empty description, the 'research.signal.what_if' naming pattern indicates this likely performs read-only scenario modeling or backtesting of trading hypotheses against market data. It does not appear to execute actual trades (no transactional/Execute markers), delete data, or move money.
From the tool's definition Tool name contains 'research.signal.what_if' which suggests a scenario analysis or simulation function that reads/queries prediction market data rather than executing trades or modifying state.
Attacks that exploit this kind of access
research.signal.what_if. It is categorised as a Read tool in the Rekko MCP MCP Server, which means it retrieves data without modifying state.
Register the Rekko MCP server in PolicyLayer and add a rule for research.signal.what_if: 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 Rekko MCP. Nothing to install.
research.signal.what_if 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 research.signal.what_if 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 research.signal.what_if. 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.
research.signal.what_if is provided by the Rekko MCP server (rekko-ai/rekko-mcp). 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 →