lock_mask

Lock or unlock a mask on a layer.

SERVERAe SOURCE@synthetic-ai/ae-mcp

Medium RISK CLASS

Category Write

Parameters 83 required

Recommended Rate-limitedsee the rule below

Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/synthetic-ai-ae-mcp/lock-mask.md

WHAT IT DOES

What lock_mask does on Ae

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

Parameter	Type	Required
`save`	boolean	—
`locked`	boolean	Yes
`compName`	string	Yes
`maskName`	string	—
`layerName`	string	Yes
`maskIndex`	number	—
`timeoutMs`	number	—
`projectPath`	string	—

Parameters from the server's own tool schema.

RISK

Why lock_mask is rated Medium

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

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs lock_mask safely

PolicyLayer is an MCP gateway: it sits between your AI agents and Ae, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For lock_mask, this is the rule to start with:

lock_mask Rate-limited

lock_mask 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": {
    "lock_mask": {
      "limits": [
        {
          "counter": "lock_mask_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 Ae, apply this rule, and every lock_mask call is checked against it from then on.

FAQ

Questions about lock_mask

What does the lock_mask tool do? +

Lock or unlock a mask on a layer. It is categorised as a Write tool in the Ae MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.

What parameters does lock_mask accept? +

lock_mask accepts 8 parameters: save, locked, compName, maskName, layerName, maskIndex, timeoutMs, projectPath. Required: locked, compName, layerName. The full parameter table on this page comes from the server's own tool schema.

How do I enforce a policy on lock_mask? +

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

What risk level is lock_mask? +

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

Can I rate-limit lock_mask? +

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

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

lock_mask is provided by the Ae MCP server (@synthetic-ai/ae-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

KEEP EXPLORING

More on Ae, and thousands of servers like it.

This server

All 226 Ae tools →

Across the catalogue

The MCP Attack Database →

Guides

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