get_issuer_details

Get detailed information about a specific issuer including all their tokens

Server RWA Pipe MCP Server rwapipe/mcp
Category Read
Risk class Low
Parameters 00 required

What get_issuer_details does on RWA Pipe MCP Server

AI agents call get_issuer_details to retrieve information from RWA Pipe MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.

Why get_issuer_details needs a policy

The tool retrieves and returns data about an issuer and their associated tokens without creating, modifying, deleting, or executing any operations. This is a read-only data retrieval operation with no side effects, fitting the 'Read' category. The severity is low as it only exposes publicly queryable blockchain data with no destructive potential or financial transaction capability.

From the tool's definition Tool name and description indicate retrieval of information: 'Get detailed information about a specific issuer including all their tokens' - this is a query operation with no modification, deletion, or execution of external commands.

Questions about get_issuer_details

What does the get_issuer_details tool do? +

Get detailed information about a specific issuer including all their tokens. It is categorised as a Read tool in the RWA Pipe MCP Server MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on get_issuer_details? +

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

What risk level is get_issuer_details? +

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

Can I rate-limit get_issuer_details? +

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

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

get_issuer_details is provided by the RWA Pipe MCP Server MCP server (rwapipe/mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

// LOOK UP ANOTHER 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 →

// GET IN TOUCH

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

Message sent.

We'll get back to you soon.