ariba_create_sourcing_project
AI agents use ariba_create_sourcing_project to create or update resources in SAP Ariba MCP Server — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your SAP Ariba MCP Server environment.
The tool creates new procurement/sourcing project data in a complex enterprise system (SAP Ariba), which is a reversible write operation. High severity is warranted because misconfigured or unintended sourcing projects could trigger unwanted procurement processes, vendor engagement, and financial commitment workflows.
From the tool's definition Tool name 'ariba_create_sourcing_project' indicates creation of a new sourcing project in SAP Ariba's procurement system. 'create' is a write operation. Description is empty, limiting certainty.
Attacks that exploit this kind of access
ariba_create_sourcing_project. It is categorised as a Write tool in the SAP Ariba MCP Server MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the SAP Ariba MCP Server MCP server in PolicyLayer and add a rule for ariba_create_sourcing_project: 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_create_sourcing_project is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.
Yes. Add a rate_limit block to the ariba_create_sourcing_project 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_create_sourcing_project. 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_create_sourcing_project 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 →