Run a single Agentforce SAST rule against the project. Useful for focused analysis. Rule IDs follow the pattern AGENTFORCE-X.Y (e.g., AGENTFORCE-1.1 for Mandatory User Confirmation).
AI agents invoke scan_agentforce_rule to trigger actions in Squirex Dev. What it does depends on the arguments the agent supplies, and its effects often reach beyond the immediate call — builds kicked off, notifications sent, workflows started.
This tool runs/executes a SAST rule scan against the project, which constitutes triggering an external operation (code analysis execution). It reads files but also actively runs analysis logic against them, making Execute the appropriate category.
From the tool's definition "Run a single Agentforce SAST rule against the project" — actively executes a static analysis scan rule against project files
Attacks that exploit this kind of access
Run a single Agentforce SAST rule against the project. Useful for focused analysis. Rule IDs follow the pattern AGENTFORCE-X.Y (e.g., AGENTFORCE-1.1 for Mandatory User Confirmation). It is categorised as a Execute tool in the Squirex Dev MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
Register the Squirex Dev MCP server in PolicyLayer and add a rule for scan_agentforce_rule: 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.
scan_agentforce_rule is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.
Yes. Add a rate_limit block to the scan_agentforce_rule 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_agentforce_rule. 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_agentforce_rule 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 →