Get detailed information about a specific Agentforce SAST rule including its description, severity, and remediation guidance.
AI agents call get_rule_details 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 retrieves and returns information about SAST security rules (description, severity, remediation guidance) without modifying, executing, or deleting any data. It is purely informational, supporting security analysis workflows by providing reference documentation. No side effects occur from invoking it.
From the tool's definition Tool name 'get_rule_details' and description 'Get detailed information about a specific Agentforce SAST rule' indicate a retrieval operation that queries metadata about security rules.
Attacks that exploit this kind of access
Get detailed information about a specific Agentforce SAST rule including its description, severity, and remediation guidance. 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 get_rule_details: 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.
get_rule_details 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 get_rule_details 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 get_rule_details. 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.
get_rule_details 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 →