// SCAN REPORT

Pypi:asqav

15 tools. 6 can modify or destroy data without limits.

1 destructive tool with no built-in limits. Policy required.

Last updated: 12 Jun 2026

6 can modify or destroy data

9 read-only

15 tools total

Community server · catalogue entry verified 12/06/2026

How to control Pypi:asqav ↓

TOOL MAP

What Pypi:asqav exposes to your agents

Read (9) Write / Execute (3) Destructive / Financial (1)

Running more than one server? Check your whole stack →

MOST DANGEROUS TOOLS

Critical Risk

The most dangerous Pypi:asqav tools

Destructive · High delete_tool_policy This tool permanently deletes enforcement policy configurations. Execute · High enforced_tool_call The name implies executing an external tool call under policy governance. Execute · High gate_action The name 'gate_action' on an AI governance server suggests this tool controls whether an action is allowed to proceed — likely triggering authorization checks or enforcement decisions that affect downstream operations. Write · High create_tool_policy The tool creates (writes) policy rules that modify the governance state of the system.

6 of Pypi:asqav's 15 tools can modify, destroy, or commit something on every call — and an agent calls them with no built-in limits.

POLICY

How to control Pypi:asqav

PolicyLayer is an MCP gateway — it sits between your AI agents and Pypi:asqav, and nothing reaches the server without passing your rules. These are the rules we recommend:

Deny destructive operations

{
  "delete_tool_policy": {
    "deny_if": [
      {
        "conditions": [],
        "on_deny": "Blocked by default. Requires approval."
      }
    ]
  }
}

Destructive tools should never be available to autonomous agents without human approval.

Rate limit write operations

{
  "create_tool_policy": {
    "limits": [
      {
        "counter": "create_tool_policy_per_hour",
        "window": "hour",
        "max": 30,
        "scope": "grant"
      }
    ]
  }
}

Prevents bulk unintended modifications from agents caught in loops.

Cap read operations

{
  "check_policy": {
    "limits": [
      {
        "counter": "check_policy_per_minute",
        "window": "minute",
        "max": 60,
        "scope": "grant"
      }
    ]
  }
}

Controls API costs and prevents retry loops from exhausting upstream rate limits.

Create a free account and register Pypi:asqav — nothing to install.
Add these rules — paste them, or build them visually. Tune the limits to your setup.
Point your MCP client (Claude, Cursor, anything) at your gateway URL.

ENFORCE POLICY ON PYPI:ASQAV →

Free to start. No card required.

FULL CATALOGUE

All 15 Pypi:asqav tools

DESTRUCTIVE 1 tools

Destructive delete_tool_policy Remove a local enforcement policy for a tool.

EXECUTE 2 tools

Execute enforced_tool_call enforced_tool_call Execute gate_action gate_action

WRITE 1 tools

Write create_tool_policy create_tool_policy

READ 9 tools

Read check_policy Check if an action is allowed by the organization's policies. Read get_agent Get details for a specific AI agent. Read list_agents List all registered AI agents in the organization. Read list_tool_policies List all active local tool enforcement policies. Read preflight_check Combined agent-status + policy-allowed check; returns CLEARED / NOT CLEARED summary. Read scan_all_tools Scan every registered tool policy for typosquatting and hidden unicode; returns a per-tool risk assessment sum Read scan_tool_definition scan_tool_definition Read verify_output verify_output Read verify_signature Verify an existing signature by signature_id.

OTHER 2 tools

Other sign_action sign_action Other complete_action complete_action

EXPLORE

Related servers

Other MCP servers with similar tools — same risk classification, starter policies for each.

FAQ

Questions about Pypi:asqav

Can an AI agent delete data through the Pypi:asqav MCP server? +

Yes. The Pypi:asqav server exposes 1 destructive tools including delete_tool_policy. These permanently remove resources with no undo. PolicyLayer blocks destructive tools by default so they never reach the upstream server.

How do I prevent bulk modifications through Pypi:asqav? +

The Pypi:asqav server has 1 write tools including create_tool_policy. Set a rate limit in your policy -- for example, 10 calls per hour prevents an agent from making more than 10 modifications per hour. PolicyLayer enforces this at the gateway, before calls reach Pypi:asqav.

How many tools does the Pypi:asqav MCP server expose? +

15 tools across 3 categories: Destructive, Read, Write. 9 are read-only. 6 can modify, create, or delete data.

How do I enforce a policy on Pypi:asqav? +

Register the Pypi:asqav MCP server in PolicyLayer, apply the suggested rules above (adjust the limits to your use case), and point your AI client at the PolicyLayer proxy URL instead of the server directly. Your agents keep the same tools; PolicyLayer evaluates every call against policy before it executes. Nothing to install, live in minutes.

Enforce policy on every Pypi:asqav tool call.

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

ENFORCE POLICY ON PYPI:ASQAV →

Free to start. No card required.

15 Pypi:asqav tools catalogued and risk-classified — across an index of 43,000+ MCP servers.