Check for Segregation of Duties violations. Optionally filter by username.
AI agents call run_sod_check to retrieve information from SyntaAI SAP Security MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
The tool performs a security audit by querying user roles and authorizations to identify SoD conflicts. It retrieves and analyzes existing data without modifying anything. Severity is medium because it accesses potentially sensitive access-control and authorization data across the SAP system, which could expose privilege structures if misused.
From the tool's definition 'Check for Segregation of Duties violations' — the tool analyzes and reports on SoD violations, optionally filtered by username. This is a read/audit operation.
Attacks that exploit this kind of access
Check for Segregation of Duties violations. Optionally filter by username. It is categorised as a Read tool in the SyntaAI SAP Security MCP Server MCP Server, which means it retrieves data without modifying state.
Register the SyntaAI SAP Security MCP Server MCP server in PolicyLayer and add a rule for run_sod_check: 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 SyntaAI SAP Security MCP Server. Nothing to install.
run_sod_check 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 run_sod_check 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 run_sod_check. 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.
run_sod_check is provided by the SyntaAI SAP Security MCP Server MCP server (syntaai/sap-security-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 →