AI agents call list_tool_policies 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 retrieves information about existing policy configurations. It performs a query operation with no side effects, no data creation, modification, or deletion, and no execution of external commands. The worst realistic misuse would be information disclosure about policies, which constitutes a low-severity read risk.
From the tool's definition The tool name is 'list_tool_policies' and the description states it 'List[s] all active local tool enforcement policies.' The verb 'list' and phrase 'list all active' indicate a read operation that retrieves and enumerates existing policies without modifying…
Documented attack patterns abuse exactly the kind of access list_tool_policies 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 list_tool_policies:
{
"version": "1",
"default": "deny",
"tools": {
"list_tool_policies": {}
}
}list_tool_policies 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.
List all active local tool enforcement policies. 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 list_tool_policies: 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.
list_tool_policies 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 list_tool_policies 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 list_tool_policies. 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.
list_tool_policies 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.