contract_disease

After a failed poison save, roll and track OSRIC

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/contract-disease.md

WHAT IT DOES

What contract_disease does on Torch-to-Crown

AI agents use contract_disease 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 contract_disease is rated Medium

An AI agent can call contract_disease 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.

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs contract_disease 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 contract_disease, this is the rule to start with:

contract_disease Rate-limited

contract_disease 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": {
    "contract_disease": {
      "limits": [
        {
          "counter": "contract_disease_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 contract_disease call is checked against it from then on.

FAQ

Questions about contract_disease

What does the contract_disease tool do? +

After a failed poison save, roll and track OSRIC. 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 contract_disease? +

Register the Torch-to-Crown MCP server in PolicyLayer and add a rule for contract_disease: 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 contract_disease? +

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

Can I rate-limit contract_disease? +

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

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

contract_disease 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

The MCP Attack Database →

Guides

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