Critical Risk →

np_squeeze

Remove single-dimensional entries

Part of the Pypi:mcp Numpy server.

np_squeeze can permanently delete data in Pypi:mcp Numpy, with no limits today. PolicyLayer puts allow, deny, and rate-limit rules on every call. Live in minutes.

SECURE PYPI:MCP NUMPY →

Free to start. No card required.

AI agents may call np_squeeze to permanently remove or destroy resources in Pypi:mcp Numpy. Without a policy, an autonomous agent could delete critical data in a loop with no way to undo the damage. PolicyLayer blocks destructive tools by default and requires explicit human approval before enabling them.

Without a policy, an AI agent could call np_squeeze in a loop, permanently destroying resources in Pypi:mcp Numpy. There is no undo for destructive operations. PolicyLayer blocks this tool by default and only allows it when a human explicitly approves the action.

Destructive tools permanently remove data. Block by default. Only enable with explicit approval workflows.

policy.json
{
  "version": "1",
  "default": "deny",
  "hide": [
    "np_squeeze"
  ]
}

See the full Pypi:mcp Numpy policy for all 29 tools.

Get this rule live on your own Pypi:mcp Numpy server in minutes. PolicyLayer enforces it on every call, before it runs.

ENFORCE ON MY PYPI:MCP NUMPY →

View all 29 tools →

These attack patterns abuse exactly the kind of access np_squeeze gives an agent. Each links to the full case and the policy that stops it:

Browse the full MCP Attack Database →

Every attack above starts with a tool call. PolicyLayer checks each one against your policy first, so np_squeeze only ever does what you allow.

SECURE PYPI:MCP NUMPY →

Other destructive tools across the catalogue. The same approach applies to each: deny by default, or require human approval.

What does the np_squeeze tool do? +

Remove single-dimensional entries. It is categorised as a Destructive tool in the Pypi:mcp Numpy 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 np_squeeze? +

Register the Pypi:mcp Numpy MCP server in PolicyLayer and add a rule for np_squeeze: 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 Pypi:mcp Numpy. Nothing to install.

What risk level is np_squeeze? +

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

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

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

np_squeeze is provided by the Pypi:mcp Numpy MCP server (pypi:mcp-numpy). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

Enforce policy on every Pypi:mcp Numpy tool call.

Deterministic rules across all 29 Pypi:mcp Numpy tools. Per-identity grants. Full audit log. Live in minutes. Nothing to install.

Free to start. No card required.

4,600+ MCP servers and 31,000+ tools scanned and risk-classified.

// GET IN TOUCH

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

Message sent.

We'll get back to you soon.