clear_guides

Remove all guides from a composition.

SERVERAe SOURCE@synthetic-ai/ae-mcp

Critical RISK CLASS

Category Destructive

Parameters 41 required

Recommended Hiddensee the rule below

Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/synthetic-ai-ae-mcp/clear-guides.md

WHAT IT DOES

What clear_guides does on Ae

AI agents call clear_guides to permanently remove resources in Ae, typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.

Parameter	Type	Required
`save`	boolean	—
`compName`	string	Yes
`timeoutMs`	number	—
`projectPath`	string	—

Parameters from the server's own tool schema.

RISK

Why clear_guides is rated Critical

An AI agent that decides to call clear_guides doesn't hesitate, doesn't double-check, and doesn't stop at one. Whatever it removes from Ae is gone. There is no undo for destructive operations.

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs clear_guides 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 clear_guides, this is the rule to start with:

clear_guides Hidden

clear_guides is removed from the agent's tool list entirely, so the agent never calls it. The rest of the server keeps working.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "hide": [
    "clear_guides"
  ]
}

RESTRICT THIS TOOL → Instant setup, no code required.

The button opens the PolicyLayer dashboard: create your workspace, connect Ae, apply this rule, and every clear_guides call is checked against it from then on.

FAQ

Questions about clear_guides

What does the clear_guides tool do? +

Remove all guides from a composition. It is categorised as a Destructive tool in the Ae MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.

What parameters does clear_guides accept? +

clear_guides accepts 4 parameters: save, compName, timeoutMs, projectPath. Required: compName. The full parameter table on this page comes from the server's own tool schema.

How do I enforce a policy on clear_guides? +

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

clear_guides is a Destructive tool with critical risk. Critical-risk tools should be blocked by default and only enabled with explicit human approval.

Can I rate-limit clear_guides? +

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

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

clear_guides 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 → Critical-risk tools on this server →

Across the catalogue

clear_renders on Why Did You Render →knowledge_clear on Templonix Lite MCP Server →clear_scan on Frida Game Hacking MCP →clear_spam_box on cPanel MCP Server → All critical-risk MCP tools → The MCP Attack Database →

Guides

Govern database agents →Blast radius →Tool call approval →