update_will · WAKE Protocol MCP: Risk & Policy

WHAT IT DOES

What update_will does on WAKE Protocol

AI agents use update_will to create or update resources in WAKE Protocol — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your WAKE Protocol environment.

WHY IT NEEDS A POLICY

Why update_will needs a policy

An AI agent can call update_will faster than any human can review — one bad instruction and it creates or modifies resources in WAKE Protocol by the hundred, each call as confident as the last.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

update_will Rate-limited

update_will 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": {
    "update_will": {
      "limits": [
        {
          "counter": "update_will_rate",
          "window": "minute",
          "max": 30,
          "scope": "grant"
        }
      ]
    }
  }
}

LIMIT THIS TOOL →

Instant setup, no code required.

PolicyLayer is an MCP gateway: every tool call is checked against your rule before it reaches WAKE Protocol, so you can run agents against it safely.

FAQ

Questions about update_will

What does the update_will tool do? +

Update fields of the WAKE Will. Requires master token. Only in ACTIVE phase. It is categorised as a Write tool in the WAKE Protocol MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.

How do I enforce a policy on update_will? +

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

What risk level is update_will? +

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

Can I rate-limit update_will? +

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

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

update_will is provided by the WAKE Protocol MCP server (wake-mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.