get_signer_details
Get detailed information about a specific signer in a PoX cycle
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.
Attacks that exploit this kind of access
The rule that runs get_signer_details safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Stacks AI MCP Server, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For get_signer_details, this is the rule to start with:
get_signer_details is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.
The button opens the PolicyLayer dashboard: create your workspace, connect Stacks AI MCP Server, apply this rule, and every get_signer_details call is checked against it from then on.
Questions about get_signer_details
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.
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.
get_signer_details is a Read tool with low risk. Read-only tools are generally safe to allow by default.
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.
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.
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.
This server
Across the catalogue