Delete a manual log type by ID.
AI agents call deleteManualLogType to permanently remove resources in Lofty MCP Server — typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
This tool permanently removes a manual log type configuration from the Lofty CRM system. Deletion of configuration/master data is irreversible and could impact workflows, reporting, and historical records that depend on this log type. While not a direct financial transaction, the blast radius is high because misconfigured or misdirected deletion could disable logging functionality for entire teams.
From the tool's definition Tool name explicitly uses 'Delete' and description states 'Delete a manual log type by ID' - irreversible data removal operation.
Attacks that exploit this kind of access
Delete a manual log type by ID. It is categorised as a Destructive tool in the Lofty MCP Server MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
Register the Lofty MCP Server MCP server in PolicyLayer and add a rule for deleteManualLogType: 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 Lofty MCP Server. Nothing to install.
deleteManualLogType is a Destructive tool with critical risk. Critical-risk tools should be blocked by default and only enabled with explicit human approval.
Yes. Add a rate_limit block to the deleteManualLogType 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 deleteManualLogType. 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.
deleteManualLogType is provided by the Lofty MCP Server MCP server (nerdsnipe-inc/lofty-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 →