get_intelligence_entity

GET /intelligence/entity/{entity}

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-intelligence-entity.md

What get_intelligence_entity does on REI Crypto MCP Server

AI agents call get_intelligence_entity 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_intelligence_entity is rated Low

This is a read-only retrieval operation that queries entity data without modifying, executing code, deleting, or moving funds. The GET HTTP method and 'get_' prefix both indicate safe data retrieval with no side effects. Low severity because unauthorized access to intelligence data poses minimal blast radius compared to write, execute, or financial operations.

From the tool's definition Tool name 'get_intelligence_entity' with GET method indicates data retrieval. Description 'GET /intelligence/entity/{entity}' confirms read-only query operation to fetch entity intelligence data from Arkham Intelligence API.

Questions about get_intelligence_entity

What does the get_intelligence_entity tool do? +

GET /intelligence/entity/{entity}. 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_intelligence_entity? +

Register the REI Crypto MCP Server MCP server in PolicyLayer and add a rule for get_intelligence_entity: 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_intelligence_entity? +

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

Can I rate-limit get_intelligence_entity? +

Yes. Add a rate_limit block to the get_intelligence_entity 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_intelligence_entity completely? +

Set action: deny in the PolicyLayer policy for get_intelligence_entity. 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_intelligence_entity? +

get_intelligence_entity 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.