remove_guide

Remove a specific guide from a composition by its 0-based index.

SERVERAe SOURCE@synthetic-ai/ae-mcp

Critical RISK CLASS

Category Destructive

Parameters 52 required

Recommended Hiddensee the rule below

Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/synthetic-ai-ae-mcp/remove-guide.md

WHAT IT DOES

What remove_guide does on Ae

AI agents call remove_guide 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	Description
`save`	boolean	—
`compName`	string	Yes
`timeoutMs`	number	—
`guideIndex`	number	Yes	0-based guide index (from list_guides)
`projectPath`	string	—

Parameters from the server's own tool schema.

RISK

Why remove_guide is rated Critical

An AI agent that decides to call remove_guide 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 remove_guide 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 remove_guide, this is the rule to start with:

remove_guide Hidden

remove_guide 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": [
    "remove_guide"
  ]
}

RESTRICT THIS TOOL → Instant setup, no code required.

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

FAQ

Questions about remove_guide

What does the remove_guide tool do? +

Remove a specific guide from a composition by its 0-based index. 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 remove_guide accept? +

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

How do I enforce a policy on remove_guide? +

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

remove_guide 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 remove_guide? +

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

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

remove_guide 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

remove_video on Mcptube Vision →remove_2fa on cPanel MCP Server →remove_concept on MegaMemory →task_assignees_remove on Vikunja → All critical-risk MCP tools → The MCP Attack Database →

Guides

Govern database agents →Blast radius →Tool call approval →