Medium Risk

mcp_aql_update

Modifying operations that overwrite data. Supported operations: edit_element, upgrade_element Element types: persona, skill, template, agent, memory, ensemble These operations modify existing data, potentially overwriting previous values. Note: Memories are append-only and do not support edit_ele...

Part of the DollhouseMCP server.

mcp_aql_update can modify DollhouseMCP data, with no limits today. PolicyLayer puts allow, deny, and rate-limit rules on every call. Live in minutes.

SECURE DOLLHOUSEMCP →

Free to start. No card required.

AI agents use mcp_aql_update to create or modify resources in DollhouseMCP. Write operations carry medium risk because an autonomous agent could trigger bulk unintended modifications. Rate limits prevent a single agent session from making hundreds of changes in rapid succession. Argument validation ensures the agent passes expected values.

Without a policy, an AI agent could call mcp_aql_update repeatedly, creating or modifying resources faster than any human could review. PolicyLayer's rate limiting ensures write operations happen at a controlled pace, and argument validation catches malformed or unexpected inputs before they reach DollhouseMCP.

Write tools can modify data. A rate limit prevents runaway bulk operations from AI agents.

policy.json
{
  "version": "1",
  "default": "deny",
  "tools": {
    "mcp_aql_update": {
      "limits": [
        {
          "counter": "mcp_aql_update_rate",
          "window": "minute",
          "max": 30,
          "scope": "grant"
        }
      ]
    }
  }
}

See the full DollhouseMCP policy for all 5 tools.

Get this rule live on your own DollhouseMCP server in minutes. PolicyLayer enforces it on every call, before it runs.

ENFORCE ON MY DOLLHOUSEMCP →

These attack patterns abuse exactly the kind of access mcp_aql_update gives an agent. Each links to the full case and the policy that stops it:

Browse the full MCP Attack Database →

Every attack above starts with a tool call. PolicyLayer checks each one against your policy first, so mcp_aql_update only ever does what you allow.

SECURE DOLLHOUSEMCP →

Other write tools across the catalogue. The same approach applies to each: rate-limit and validate the arguments.

What does the mcp_aql_update tool do? +

Modifying operations that overwrite data. Supported operations: edit_element, upgrade_element Element types: persona, skill, template, agent, memory, ensemble These operations modify existing data, potentially overwriting previous values. Note: Memories are append-only and do not support edit_element. Use addEntry (CREATE) to add new entries. Quick start example: { operation: "edit_element", element_type: "persona", params: { element_name: "MyPersona", input: { description: "Updated description" } } } { operation: "edit_element", element_type: "persona", params: { element_name: "Friendly-Teacher", input: { instructions: "Updated behavioral directives." } } } { operation: "edit_element", element_type: "agent", params: { element_name: "code-reviewer", input: { instructions: "Updated agent behavioral profile.", goal: { template: "Complete: {task}" } } } } { operation: "upgrade_element", element_type: "agent", params: { element_name: "task-planner" } } Discover required parameters — use mcp_aql_read: { operation: "introspect", params: { query: "operations", name: "edit_element" } }. It is categorised as a Write tool in the DollhouseMCP MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.

How do I enforce a policy on mcp_aql_update? +

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

What risk level is mcp_aql_update? +

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

Can I rate-limit mcp_aql_update? +

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

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

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

Enforce policy on every DollhouseMCP tool call.

Deterministic rules across all 5 DollhouseMCP tools. Per-identity grants. Full audit log. Live in minutes. Nothing to install.

Free to start. No card required.

4,600+ MCP servers and 31,000+ tools scanned and risk-classified.

// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.