Create one or more blocks under a parent block or page
AI agents use create_block to create or update resources in Wolai MCP Server — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Wolai MCP Server environment.
Creating blocks modifies the knowledge base structure and content in a way that persists and represents a write operation. While reversible (blocks can be deleted), this is a content creation action that alters the state of the system. Severity is medium because the blast radius is limited to the Wolai knowledge base—no external systems, financial impact, or destructive data loss occurs.
From the tool's definition Tool name 'create_block' and description 'Create one or more blocks under a parent block or page' indicate irreversible content creation.
Attacks that exploit this kind of access
Create one or more blocks under a parent block or page. It is categorised as a Write tool in the Wolai MCP Server MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Wolai MCP Server MCP server in PolicyLayer and add a rule for create_block: 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 Wolai MCP Server. Nothing to install.
create_block is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.
Yes. Add a rate_limit block to the create_block 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.
Set action: deny in the PolicyLayer policy for create_block. 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.
create_block is provided by the Wolai MCP Server MCP server (wuchaoli/wolai-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Every MCP server has a record like this.
Type a name, get the same breakdown: verified identity, auth posture, risk grade, capabilities, recommended policy.
Teams ship this data inside their own products. See what a licence covers →