mlmh_delete_search_preset

Delete a saved search preset by name.

Server FluentCommunity Manager wplaunchify/fluent-community-mcp
Category Destructive
Risk class Critical
Parameters 00 required

What mlmh_delete_search_preset does on FluentCommunity Manager

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

Why mlmh_delete_search_preset needs a policy

The tool permanently removes a saved search preset, which cannot be undone. This fits the Destructive category definition: 'irreversibly deletes or overwrites data, or actions that cannot be undone.' While the blast radius is limited (only search presets are affected, not primary content), the irreversible nature and potential for accidental loss of saved searches justifies medium severity.

From the tool's definition Tool name 'mlmh_delete_search_preset' explicitly contains 'delete' and description states 'Delete a saved search preset by name.' This is an irreversible deletion operation.

Questions about mlmh_delete_search_preset

What does the mlmh_delete_search_preset tool do? +

Delete a saved search preset by name. It is categorised as a Destructive tool in the FluentCommunity Manager MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.

How do I enforce a policy on mlmh_delete_search_preset? +

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

What risk level is mlmh_delete_search_preset? +

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

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

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

mlmh_delete_search_preset is provided by the FluentCommunity Manager MCP server (wplaunchify/fluent-community-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

// LOOK UP ANOTHER 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 →

// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.