New Your team’s decisions, in one playbook every coding agent works from. Never answer your agent twice

get_signer_details

Get detailed information about a specific signer in a PoX cycle

SERVERStacks AI MCP Server SOURCEstack-ai-mcp/stacks-mcp-server
Low RISK CLASS
Category Read
Parameters 00 required
Recommended Allowedsee the rule below
Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/stack-ai-mcp-stacks-mcp-server/get-signer-details.md

What get_signer_details does on Stacks AI MCP Server

AI agents call get_signer_details to retrieve information from Stacks AI 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_signer_details is rated Low

This tool retrieves and returns information about a signer in a Proof-of-Transfer (PoX) cycle. The verb 'Get' and the read-only nature of querying signer details (no state changes, no financial transactions, no code execution) clearly classify this as a Read operation. The severity is low as it only exposes publicly queryable blockchain data with no side effects or security implications from misuse.

From the tool's definition Tool name 'get_signer_details' and description 'Get detailed information about a specific signer in a PoX cycle' indicate a retrieval operation that queries blockchain state data without modification or execution of transactions.

Questions about get_signer_details

What does the get_signer_details tool do? +

Get detailed information about a specific signer in a PoX cycle. It is categorised as a Read tool in the Stacks AI MCP Server MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on get_signer_details? +

Register the Stacks AI MCP Server MCP server in PolicyLayer and add a rule for get_signer_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 Stacks AI MCP Server. Nothing to install.

What risk level is get_signer_details? +

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

Can I rate-limit get_signer_details? +

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

Set action: deny in the PolicyLayer policy for get_signer_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_signer_details? +

get_signer_details is provided by the Stacks AI MCP Server MCP server (stack-ai-mcp/stacks-mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

More on Stacks AI 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 Stacks AI 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.