Returns current signing configuration and pubkey
AI agents call getSignerInfo to retrieve information from Nostr Tools for AI Agents without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool queries and returns information about the current signing configuration and public key. It performs a read-only operation with no side effects—it retrieves data without creating, modifying, deleting, or executing any operations. The blast radius if misused is minimal, as it only exposes configuration metadata.
From the tool's definition Tool name 'getSignerInfo' and description 'Returns current signing configuration and pubkey' indicate data retrieval with no modification or execution of external operations.
Attacks that exploit this kind of access
Returns current signing configuration and pubkey. It is categorised as a Read tool in the Nostr Tools for AI Agents MCP Server, which means it retrieves data without modifying state.
Register the Nostr Tools for AI Agents MCP server in PolicyLayer and add a rule for getSignerInfo: 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 Nostr Tools for AI Agents. Nothing to install.
getSignerInfo 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 getSignerInfo 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 getSignerInfo. 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.
getSignerInfo is provided by the Nostr Tools for AI Agents MCP server (jorgenclaw/nostr-mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the 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 →