ariba_supplier_filter_by_status
AI agents call ariba_supplier_filter_by_status 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.
The tool name strongly suggests querying or retrieving supplier data filtered by status, which is a Read operation with no side effects. The 'filter_by' pattern is characteristic of data retrieval. Without a description, confidence is moderate but not reduced further because the name provides clear semantic intent.
From the tool's definition Tool name 'ariba_supplier_filter_by_status' indicates a filtering/query operation on supplier data by status. The name pattern aligns with retrieval operations ('filter_by' pattern common in Read operations).
Attacks that exploit this kind of access
ariba_supplier_filter_by_status. 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_supplier_filter_by_status: 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_supplier_filter_by_status 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_supplier_filter_by_status 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_supplier_filter_by_status. 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_supplier_filter_by_status 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 →