get_tag_params

GET /tag/{id}/params

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-tag-params.md

WHAT IT DOES

What get_tag_params does on REI Crypto MCP Server

AI agents call get_tag_params 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.

RISK

Why get_tag_params is rated Low

This is a straightforward read operation that queries tag parameters from a crypto data API. It retrieves information without creating, modifying, deleting, or executing any operations. The sibling tools all follow similar read-only patterns (get_balances, get_batch_historical_prices, get_bridge_details, etc.), consistent with a data retrieval API.

From the tool's definition Tool is a GET endpoint that retrieves parameters for a tag by ID (/tag/{id}/params). GET requests are non-mutating read operations. The tool name 'get_tag_params' and HTTP method confirm data retrieval without side effects.

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs get_tag_params safely

PolicyLayer is an MCP gateway: it sits between your AI agents and REI Crypto MCP Server, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For get_tag_params, this is the rule to start with:

get_tag_params Allowed

get_tag_params is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "get_tag_params": {}
  }
}

ALLOW ONLY THIS TOOL → Instant setup, no code required.

The button opens the PolicyLayer dashboard: create your workspace, connect REI Crypto MCP Server, apply this rule, and every get_tag_params call is checked against it from then on.

FAQ

Questions about get_tag_params

What does the get_tag_params tool do? +

GET /tag/{id}/params. 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_tag_params? +

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

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

Can I rate-limit get_tag_params? +

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

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

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

KEEP EXPLORING

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

This server

All 117 REI Crypto MCP Server tools →

Across the catalogue

get_cocktail_by_category on Cocktails RAG MCP Server →get_torrent_detail on M-Team MCP Server →aiva_get_affiliate on AIVA MCP Server →get-chuck-categories on Jokes MCP Server → The MCP Attack Database →

Guides

Roll out MCP under one policy →Data exfiltration →MCP token cost →