High Risk →

apiosk_wallet_reveal_secret

Reveal a local wallet's private key. Only call this when the user explicitly asks to see the secret key.

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

apiosk-mcp-server Execute Risk 3/5

AI agents invoke apiosk_wallet_reveal_secret to trigger processes or run actions in Apiosk. Execute operations can have side effects beyond the immediate call -- triggering builds, sending notifications, or starting workflows. Rate limits and argument validation are essential to prevent runaway execution.

apiosk_wallet_reveal_secret can trigger processes with real-world consequences. An uncontrolled agent might start dozens of builds, send mass notifications, or kick off expensive compute jobs. Intercept enforces rate limits and validates arguments to keep execution within safe bounds.

Execute tools trigger processes. Rate-limit and validate arguments to prevent unintended side effects.

apiosk.yaml
tools:
  apiosk_wallet_reveal_secret:
    rules:
      - action: allow
        rate_limit:
          max: 10
          window: 60
        validate:
          required_args: true

See the full Apiosk policy for all 160 tools.

Tool Name apiosk_wallet_reveal_secret
Category Execute
MCP Server Apiosk MCP Server
Risk Level High

View all 160 tools →

Agents calling execute-class tools like apiosk_wallet_reveal_secret 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 Execute risk category across the catalogue. The same policy patterns (rate-limit, validate) apply to each.

apiosk_wallet_reveal_secret is one of the high-risk operations in Apiosk. For the full severity-focused view — only the high-risk tools with their recommended policies — see the breakdown for this server, or browse all high-risk tools across every MCP server.

What does the apiosk_wallet_reveal_secret tool do? +

Reveal a local wallet's private key. Only call this when the user explicitly asks to see the secret key.. It is categorised as a Execute tool in the Apiosk MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.

How do I enforce a policy on apiosk_wallet_reveal_secret? +

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

What risk level is apiosk_wallet_reveal_secret? +

apiosk_wallet_reveal_secret is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.

Can I rate-limit apiosk_wallet_reveal_secret? +

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

Set action: deny in the Intercept policy for apiosk_wallet_reveal_secret. 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 apiosk_wallet_reveal_secret? +

apiosk_wallet_reveal_secret is provided by the Apiosk MCP server (apiosk-mcp-server). Intercept sits as a proxy in front of this server to enforce policies before tool calls reach the server.

Enforce policies on Apiosk

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.