updateDevice · Memnote MCP: Risk & Policy

WHAT IT DOES

What updateDevice does on Memnote

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

PARAMETERS

Parameter	Type	Required	Description
`id`	string	Yes
`body`	object	Yes

Parameters from the server's own tool schema.

WHY IT NEEDS A POLICY

Why updateDevice needs a policy

This tool modifies device configuration or metadata, which is a Write-category operation. Severity is medium because device updates could affect system behavior or settings, but the impact depends on what device properties can be modified. Confidence is 0.85 rather than higher because the description lacks detail about which device properties are modifiable and the scope of potential changes.

From the tool's definition Tool name 'updateDevice' with description 'Update a device' indicates modification of existing device data. The verb 'update' is a reversible write operation.

Risk signalsAccepts raw HTML/template content (body)

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

updateDevice Rate-limited

updateDevice 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": {
    "updateDevice": {
      "limits": [
        {
          "counter": "updatedevice_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 Memnote, so you can run agents against it safely.

FAQ

Questions about updateDevice

What does the updateDevice tool do? +

Update a device. It is categorised as a Write tool in the Memnote MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.

What parameters does updateDevice accept? +

updateDevice accepts 2 parameters: id, body. Required: id, body. The full parameter table on this page comes from the server's own tool schema.

How do I enforce a policy on updateDevice? +

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

What risk level is updateDevice? +

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

Can I rate-limit updateDevice? +

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

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

updateDevice is provided by the Memnote MCP server (@randomfact/memnote-mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.