resolve_stinking_cloud

SERVERTorch-to-Crown SOURCEDiogenes187/Torch-to-Crown

Medium RISK CLASS

Category Write

Parameters 00 required

Recommended Rate-limitedsee the rule below

Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/torch-to-crown/resolve-stinking-cloud.md

WHAT IT DOES

What resolve_stinking_cloud does on Torch-to-Crown

AI agents use resolve_stinking_cloud to create or update resources in Torch-to-Crown, usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Torch-to-Crown environment.

RISK

Why resolve_stinking_cloud is rated Medium

An AI agent can call resolve_stinking_cloud faster than any human can review: one bad instruction and it creates or modifies resources in Torch-to-Crown by the hundred, each call as confident as the last.

Risk signalsBulk/mass operation — affects multiple targets

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs resolve_stinking_cloud safely

PolicyLayer is an MCP gateway: it sits between your AI agents and Torch-to-Crown, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For resolve_stinking_cloud, this is the rule to start with:

resolve_stinking_cloud Rate-limited

resolve_stinking_cloud stays usable, but capped: an agent stuck in a loop can't make hundreds of changes a minute. Everything else on the server is denied unless you say otherwise.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "resolve_stinking_cloud": {
      "limits": [
        {
          "counter": "resolve_stinking_cloud_rate",
          "window": "minute",
          "max": 30,
          "scope": "grant"
        }
      ]
    }
  }
}

LIMIT THIS TOOL → Instant setup, no code required.

The button opens the PolicyLayer dashboard: create your workspace, connect Torch-to-Crown, apply this rule, and every resolve_stinking_cloud call is checked against it from then on.

FAQ

Questions about resolve_stinking_cloud

What does the resolve_stinking_cloud tool do? +

Resolve a declared 20ft-radius Stinking Cloud for 1 round per caster level. Every listed creature caught initially saves vs spells: failure means 1d4+1 rounds stunned and unable to act; success still means one round stunned in which it may only leave the cloud as fast as possible. Use resolve_stinking_cloud_entry for later entrants. It is categorised as a Write tool in the Torch-to-Crown MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.

How do I enforce a policy on resolve_stinking_cloud? +

Register the Torch-to-Crown MCP server in PolicyLayer and add a rule for resolve_stinking_cloud: 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 Torch-to-Crown. Nothing to install.

What risk level is resolve_stinking_cloud? +

resolve_stinking_cloud is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.

Can I rate-limit resolve_stinking_cloud? +

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

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

resolve_stinking_cloud is provided by the Torch-to-Crown MCP server (Diogenes187/Torch-to-Crown). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

KEEP EXPLORING

More on Torch-to-Crown, and thousands of servers like it.

This server

All 451 Torch-to-Crown tools →

Across the catalogue

resolve_circuit on 0gzk → The MCP Attack Database →

Guides

Govern customer-ops agents →Argument validation →Scoped token →