Mark a split as validated for MECE (Mutually Exclusive, Collectively Exhaustive) properties. The tile must have children.
AI agents use mark_mece to create or update resources in Tiling Trees MCP Server — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Tiling Trees MCP Server environment.
This tool creates or modifies data in a reversible manner (marking a tile with a validation status can be unmarked or changed). It does not retrieve data (Read), execute arbitrary code (Execute), permanently delete data (Destructive), or involve financial transactions (Financial).
From the tool's definition The tool 'mark_mece' performs a state update operation: it marks a split tile with a validation status for MECE properties.
Attacks that exploit this kind of access
Mark a split as validated for MECE (Mutually Exclusive, Collectively Exhaustive) properties. The tile must have children. It is categorised as a Write tool in the Tiling Trees MCP Server MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Tiling Trees MCP Server MCP server in PolicyLayer and add a rule for mark_mece: 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 Tiling Trees MCP Server. Nothing to install.
mark_mece 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 mark_mece 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 mark_mece. 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.
mark_mece is provided by the Tiling Trees MCP Server MCP server (k-chrispens/tiling-trees-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 →