AI agents call paserver_remove to permanently remove resources in Claude Pascal MCP Server — typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
The tool name contains 'remove', which is a destructive verb. In the context of server management and application lifecycle tools, removing a server component is irreversible and has high blast radius if invoked incorrectly by an AI agent. The empty description lowers confidence slightly, but the clear destructive verb and context warrant classification as Destructive with critical severity.
From the tool's definition Tool name 'paserver_remove' suggests deletion/removal of a Pascal/Delphi application server component. The sibling tools include ADB functions (adb_push, adb_install, adb_pull, adb_stop_app) indicating interaction with Android devices and applications.
Documented attack patterns abuse exactly the kind of access paserver_remove gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Claude Pascal MCP Server, and nothing reaches the server without passing your rules. This is the rule we recommend for paserver_remove:
{
"version": "1",
"default": "deny",
"hide": [
"paserver_remove"
]
}paserver_remove disappears from the agent's tool list entirely, and any attempt to call it is denied. The rest of the server keeps working.
Free to start. No card required.
paserver_remove. It is categorised as a Destructive tool in the Claude Pascal MCP Server MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
Register the Claude Pascal MCP Server MCP server in PolicyLayer and add a rule for paserver_remove: 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 Claude Pascal MCP Server. Nothing to install.
paserver_remove 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 paserver_remove 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 paserver_remove. 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.
paserver_remove is provided by the Claude Pascal MCP Server MCP server (tina4stack/claude-pascal-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from Claude Pascal MCP Server, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.
Free to start. No card required.
53 Claude Pascal MCP Server tools catalogued and risk-classified — across an index of 43,000+ MCP servers.