delete_log_source

Delete a registered log source.

Server MCP Log Analyzer sedwardstx/demomcp
Category Destructive
Risk class Critical
Parameters 00 required

What delete_log_source does on MCP Log Analyzer

AI agents call delete_log_source to permanently remove resources in MCP Log Analyzer — typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.

Why delete_log_source needs a policy

The tool performs an irreversible deletion operation on system log source configurations. Once a log source is deleted, the registration and any associated metadata cannot be recovered without manual re-registration. This qualifies as Destructive rather than Write (which is reversible).

From the tool's definition Tool name explicitly uses 'delete' verb and description states 'Delete a registered log source' — this irreversibly removes a log source registration from the system.

Questions about delete_log_source

What does the delete_log_source tool do? +

Delete a registered log source. It is categorised as a Destructive tool in the MCP Log Analyzer 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 delete_log_source? +

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

What risk level is delete_log_source? +

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

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

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

delete_log_source is provided by the MCP Log Analyzer MCP server (sedwardstx/demomcp). 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.