AI agents call research.pipe.get 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 'get' suffix strongly suggests a read operation retrieving pipe/research data. However, without a clear description, confidence is moderate. Given the server's focus on market intelligence and research (not execution or trading), this appears to be a data retrieval tool.
From the tool's definition Tool name 'research.pipe.get' uses the 'get' verb, which typically indicates data retrieval. The server context involves prediction market intelligence and research signals. The description is empty, making full assessment difficult.
Attacks that exploit this kind of access
research.pipe.get. 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.get: 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.get 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.get 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.get. 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.get 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 →