ariba_sda_filter_suppliers
AI agents call ariba_sda_filter_suppliers 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.
Filtering suppliers is a read operation that retrieves data without side effects. However, severity is elevated to 'medium' because supplier data in SAP Ariba is business-critical for procurement decisions; an AI agent with access to filter and enumerate suppliers could conduct reconnaissance on the business network or identify sensitive supplier relationships.
From the tool's definition Tool name 'ariba_sda_filter_suppliers' indicates filtering/querying suppliers, which is a retrieval operation. The 'filter' operation suggests searching or listing suppliers based on criteria rather than modifying or deleting them.
Attacks that exploit this kind of access
ariba_sda_filter_suppliers. 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_sda_filter_suppliers: 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_sda_filter_suppliers 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_sda_filter_suppliers 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_sda_filter_suppliers. 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_sda_filter_suppliers 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 →