ariba_audit_search_by_actor
AI agents call ariba_audit_search_by_actor to retrieve information from SAP Ariba MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
Audit search functionality retrieves historical records and logs—a read operation with no side effects. Confidence is moderate (0.75) rather than high because the description is empty, leaving some ambiguity about whether it might expose sensitive audit data at scale or with restricted access implications.
From the tool's definition Tool name 'ariba_audit_search_by_actor' indicates a search operation on audit logs or records, which is a read-only retrieval action. The '_search_by_' pattern and 'audit' context suggest querying existing data without modification.
Attacks that exploit this kind of access
ariba_audit_search_by_actor. It is categorised as a Read tool in the SAP Ariba MCP Server MCP Server, which means it retrieves data without modifying state.
Register the SAP Ariba MCP Server MCP server in PolicyLayer and add a rule for ariba_audit_search_by_actor: 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 SAP Ariba MCP Server. Nothing to install.
ariba_audit_search_by_actor 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 ariba_audit_search_by_actor 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 ariba_audit_search_by_actor. 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.
ariba_audit_search_by_actor is provided by the SAP Ariba MCP Server MCP server (vanshikadhole/mcpserver). 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 →