sessions_remove_attack

sessions_remove_attack

Server CyPerf MCP Server keysight/cyperf-mcp
Category Destructive
Risk class Critical
Parameters 00 required

What sessions_remove_attack does on CyPerf MCP Server

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

Why sessions_remove_attack needs a policy

The tool performs a removal operation on sessions, which is destructive by nature—data deletion cannot be undone. While the description is empty (lowering confidence slightly), the name clearly indicates a delete/remove action in the context of security testing sessions. Destructive severity is assigned because deleted sessions cannot be recovered and represent irreversible loss of test configuration or results.

From the tool's definition Tool name 'sessions_remove_attack' indicates removal/deletion of attack sessions. The 'remove' verb combined with the testing context (CyPerf network security testing) suggests irreversible deletion of test data or session state.

Questions about sessions_remove_attack

What does the sessions_remove_attack tool do? +

sessions_remove_attack. It is categorised as a Destructive tool in the CyPerf MCP Server 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 sessions_remove_attack? +

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

What risk level is sessions_remove_attack? +

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

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

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

sessions_remove_attack is provided by the CyPerf MCP Server MCP server (keysight/cyperf-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.