Scan every registered tool policy for typosquatting and hidden unicode; returns a per-tool risk assessment summary.
AI agents call scan_all_tools to retrieve information from Pypi:asqav without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool performs a security audit by examining existing tool policies for vulnerabilities (typosquatting, hidden unicode). It has no side effects—it reads policy configurations and produces a report. No data is created, modified, deleted, or executed. This is a classic Read operation: passive analysis of existing state with informational output.
From the tool's definition Tool description states it 'returns a per-tool risk assessment summary' via scanning, with no indication of data modification, deletion, or external execution. The word 'scan' and 'returns' indicate query/inspection operations.
Risk signalsBulk/mass operation — affects multiple targets
Documented attack patterns abuse exactly the kind of access scan_all_tools gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Pypi:asqav, and nothing reaches the server without passing your rules. This is the rule we recommend for scan_all_tools:
{
"version": "1",
"default": "deny",
"tools": {
"scan_all_tools": {}
}
}scan_all_tools is read-only, so it stays allowed — but everything else on the server is denied unless you say otherwise.
Free to start. No card required.
Scan every registered tool policy for typosquatting and hidden unicode; returns a per-tool risk assessment summary. It is categorised as a Read tool in the Pypi:asqav MCP Server, which means it retrieves data without modifying state.
Register the Pypi:asqav MCP server in PolicyLayer and add a rule for scan_all_tools: 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:asqav. Nothing to install.
scan_all_tools is a Read tool with low risk. Read-only tools are generally safe to allow by default.
Yes. Add a rate_limit block to the scan_all_tools 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 scan_all_tools. 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.
scan_all_tools is provided by the Pypi:asqav MCP server (jagmarques/asqav-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from Pypi:asqav, 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.
15 Pypi:asqav tools catalogued and risk-classified — across an index of 43,000+ MCP servers.