List all 26 Agentforce Capability Scanner rules with their ID, name, category, severity, and description. Use this to understand the full scope of the security scan.
AI agents call list_scan_rules to retrieve information from Squirex Dev without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool only retrieves and displays metadata about security scanning rules. It performs a read operation with no side effects, reversible actions, code execution, data destruction, or financial impact. The low severity reflects that misuse would at most return informational data about security rules, posing minimal risk to the system or data.
From the tool's definition Tool name and description indicate it 'List[s] all 26 Agentforce Capability Scanner rules' and is explicitly described as a query to 'understand the full scope' without modifying or executing anything.
Attacks that exploit this kind of access
List all 26 Agentforce Capability Scanner rules with their ID, name, category, severity, and description. Use this to understand the full scope of the security scan. It is categorised as a Read tool in the Squirex Dev MCP Server, which means it retrieves data without modifying state.
Register the Squirex Dev MCP server in PolicyLayer and add a rule for list_scan_rules: 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 Squirex Dev. Nothing to install.
list_scan_rules 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_scan_rules 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_scan_rules. 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_scan_rules is provided by the Squirex Dev MCP server (squirex-dev/squirex-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the 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 →