Scan a specific Agentforce metadata file for capability violations. Supports .genAiFunction-meta.xml, .genAiPlugin-meta.xml, .genAiPlannerBundle-meta.xml, .genAiPromptTemplate-meta.xml, .agent files, .cls (Apex), .trigger, and schema.json files.
AI agents call scan_agentforce_file 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 reads and analyzes Salesforce Agentforce metadata files using SAST (Static Application Security Testing) rules to identify vulnerabilities. It performs static analysis—examining file contents to detect security issues—without modifying files, executing code, or triggering external operations. The scan operation is intrinsically a read/analysis activity.
From the tool's definition Tool performs scanning and analysis of metadata files for vulnerability detection. Description uses terms like 'scan' and 'for capability violations' which indicate analysis without modification or execution of code.
Attacks that exploit this kind of access
Scan a specific Agentforce metadata file for capability violations. Supports .genAiFunction-meta.xml, .genAiPlugin-meta.xml, .genAiPlannerBundle-meta.xml, .genAiPromptTemplate-meta.xml, .agent files, .cls (Apex), .trigger, and schema.json files. 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 scan_agentforce_file: 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_file 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_agentforce_file 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_file. 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_file 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 →