createDevice · Memnote MCP: Risk & Policy

WHAT IT DOES

What createDevice does on Memnote

AI agents use createDevice 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
`body`	object	Yes

Parameters from the server's own tool schema.

WHY IT NEEDS A POLICY

Why createDevice needs a policy

This is a Write operation as it creates a new device entity in the system. Severity is medium because device creation could affect system configuration and potentially enable unauthorized access paths, but it is reversible (can be deleted via sibling deleteDevice tool if available).

From the tool's definition Tool name 'createDevice' indicates creation of a new device resource. Description states 'Create a device', confirming irreversible addition of a data record.

Risk signalsAccepts raw HTML/template content (body)

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

createDevice Rate-limited

createDevice 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": {
    "createDevice": {
      "limits": [
        {
          "counter": "createdevice_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 createDevice

What does the createDevice tool do? +

Create 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 createDevice accept? +

createDevice accepts 1 parameter: body. Required: body. The full parameter table on this page comes from the server's own tool schema.

How do I enforce a policy on createDevice? +

Register the Memnote MCP server in PolicyLayer and add a rule for createDevice: 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 createDevice? +

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

Can I rate-limit createDevice? +

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

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

createDevice 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.