ariba_asset_list_requisitions
AI agents call ariba_asset_list_requisitions 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.
This tool appears to retrieve or enumerate requisition records from SAP Ariba's procurement system. Listing requisitions is a query operation with no side effects—it does not modify, delete, or execute actions on data. The blast radius of misuse is limited to unauthorized data exposure.
From the tool's definition Tool name 'ariba_asset_list_requisitions' contains 'list', which is a retrieval operation that queries requisitions data. The description is empty, but the naming pattern is consistent with Read operations (search, list, get, fetch).
Attacks that exploit this kind of access
ariba_asset_list_requisitions. 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_asset_list_requisitions: 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_asset_list_requisitions 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_asset_list_requisitions 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_asset_list_requisitions. 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_asset_list_requisitions 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 →