GET /approvables/{approvableId}
AI agents call ariba_approval_get_approvable 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 is a read operation that retrieves approval-related data (approvables) without creating, modifying, or deleting information. However, severity is elevated to 'medium' because approvables in procurement systems likely contain sensitive business data (contracts, sourcing decisions, supplier evaluations, financial commitments).
From the tool's definition Tool name 'ariba_approval_get_approvable' and HTTP method GET indicate data retrieval. Description shows a GET endpoint that retrieves a specific approvable resource by ID, with no modification or side effects.
Attacks that exploit this kind of access
GET /approvables/{approvableId}. 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_approval_get_approvable: 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_approval_get_approvable 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_approval_get_approvable 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_approval_get_approvable. 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_approval_get_approvable 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 →