Low Risk

getSignerInfo

Returns current signing configuration and pubkey

Part of the Nostr_AI_Tools_Jorgenclaw MCP server. Enforce policies on this tool with Intercept, the open-source MCP proxy.

AI agents call getSignerInfo to retrieve information from Nostr_AI_Tools_Jorgenclaw without modifying any data. This is common in research, monitoring, and reporting workflows where the agent needs context before taking action. Because read operations don't change state, they are generally safe to allow without restrictions -- but you may still want rate limits to control API costs.

Even though getSignerInfo only reads data, uncontrolled read access can leak sensitive information or rack up API costs. An agent caught in a retry loop could make thousands of calls per minute. A rate limit gives you a safety net without blocking legitimate use.

Read-only tools are safe to allow by default. No rate limit needed unless you want to control costs.

nostr-ai-tools-jorgenclaw-nostr-ai-tools-jorgenclaw.yaml
tools:
  getSignerInfo:
    rules:
      - action: allow

See the full Nostr_AI_Tools_Jorgenclaw policy for all 23 tools.

Tool Name getSignerInfo
Category Read
Risk Level Low

View all 23 tools →

Agents calling read-class tools like getSignerInfo have been implicated in these attack patterns. Read the full case and prevention policy for each:

Browse the full MCP Attack Database →

Other tools in the Read risk category across the catalogue. The same policy patterns (rate-limit, allow) apply to each.

What does the getSignerInfo tool do? +

Returns current signing configuration and pubkey. It is categorised as a Read tool in the Nostr_AI_Tools_Jorgenclaw MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on getSignerInfo? +

Add a rule in your Intercept YAML policy under the tools section for getSignerInfo. You can allow, deny, rate-limit, or validate arguments. Then run Intercept as a proxy in front of the Nostr_AI_Tools_Jorgenclaw MCP server.

What risk level is getSignerInfo? +

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

Can I rate-limit getSignerInfo? +

Yes. Add a rate_limit block to the getSignerInfo rule in your Intercept 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 getSignerInfo completely? +

Set action: deny in the Intercept 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.

What MCP server provides getSignerInfo? +

getSignerInfo is provided by the Nostr_AI_Tools_Jorgenclaw MCP server (Nostr_AI_Tools_Jorgenclaw/Nostr_AI_Tools_Jorgenclaw). Intercept sits as a proxy in front of this server to enforce policies before tool calls reach the server.

Enforce policies on Nostr_AI_Tools_Jorgenclaw

Open source. One binary. Zero dependencies.

npx -y @policylayer/intercept
github.com/policylayer/intercept →
// GET IN TOUCH

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

Message sent.

We'll get back to you soon.