get_protocol_inflows

GET /api/inflows/{protocol}/{timestamp}

SERVERREI Crypto MCP Server SOURCE0xreisearch/crypto-mcp-beta
Low RISK CLASS
Category Read
Parameters 00 required
Recommended Allowedsee the rule below
Registry record Grade B, identity unverified Pull the record →

This record as markdown: /tools/0xreisearch-crypto-mcp-beta/get-protocol-inflows.md

What get_protocol_inflows does on REI Crypto MCP Server

AI agents call get_protocol_inflows to retrieve information from REI Crypto MCP Server without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.

Why get_protocol_inflows is rated Low

This tool retrieves inflow data for a specified protocol at a given timestamp. It has no side effects, modifies no data, executes no code, and incurs no financial obligations. It is purely a data query operation consistent with the 'Read' category. Severity is low because unauthorized access to historical protocol inflow metrics poses minimal risk compared to tools that could execute arbitrary queries or modify data.

From the tool's definition Tool name 'get_protocol_inflows' with GET method and description 'GET /api/inflows/{protocol}/{timestamp}' indicates data retrieval operation. The HTTP GET verb and 'get_' prefix confirm read-only semantics.

Questions about get_protocol_inflows

What does the get_protocol_inflows tool do? +

GET /api/inflows/{protocol}/{timestamp}. It is categorised as a Read tool in the REI Crypto MCP Server MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on get_protocol_inflows? +

Register the REI Crypto MCP Server MCP server in PolicyLayer and add a rule for get_protocol_inflows: 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 REI Crypto MCP Server. Nothing to install.

What risk level is get_protocol_inflows? +

get_protocol_inflows is a Read tool with low risk. Read-only tools are generally safe to allow by default.

Can I rate-limit get_protocol_inflows? +

Yes. Add a rate_limit block to the get_protocol_inflows 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.

How do I block get_protocol_inflows completely? +

Set action: deny in the PolicyLayer policy for get_protocol_inflows. 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.

What MCP server provides get_protocol_inflows? +

get_protocol_inflows is provided by the REI Crypto MCP Server MCP server (0xreisearch/crypto-mcp-beta). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

More on REI Crypto MCP Server, and thousands of servers like it.

// THE MCP REGISTRY

PolicyLayer tracks 44,603 MCP servers and 515,000+ tools.

Every server has a live record: who publishes it, whether it answers without auth, its risk grade, every tool classified, the recommended policy. This page is one line of REI Crypto MCP Server's. Pull the full record:

Teams ship this data inside their own products. See what a licence covers →

// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.