AI agents call research.pipe.status 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.
The naming convention indicates this tool likely retrieves the status of a research pipeline, consistent with Read operations that query state without modifying data. Given the server's focus on prediction market intelligence and the sibling tools handling data retrieval (market.data.get, market.data.list, analytics.report), a status check fits the Read category.
From the tool's definition Tool name 'research.pipe.status' suggests a status check or monitoring operation typical of read-only queries. The description is empty, limiting direct evidence.
Attacks that exploit this kind of access
research.pipe.status. 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.pipe.status: 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.pipe.status 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.pipe.status 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.pipe.status. 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.pipe.status 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 →