ariba_contract_compliance_update_request

WHAT IT DOES

What ariba_contract_compliance_update_request does on SAP Ariba MCP Server

AI agents use ariba_contract_compliance_update_request 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.

WHY IT NEEDS A POLICY

Why ariba_contract_compliance_update_request needs a policy

This tool creates or modifies contract request data reversibly through a PATCH operation. While it modifies business-critical procurement data (contracts), the operation is not irreversible (data can be further updated), does not delete data, and does not involve financial transactions directly.

From the tool's definition Tool name contains 'update_request' and description indicates PATCH operation on contractRequests resource, which modifies contract request data. PATCH is an HTTP method for partial updates.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

ariba_contract_compliance_update_request Rate-limited

ariba_contract_compliance_update_request stays usable, but capped — an agent stuck in a loop can't make hundreds of changes a minute. Everything else on the server is denied unless you say otherwise.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "ariba_contract_compliance_update_request": {
      "limits": [
        {
          "counter": "ariba_contract_compliance_update_request_rate",
          "window": "minute",
          "max": 30,
          "scope": "grant"
        }
      ]
    }
  }
}

LIMIT THIS TOOL →

Instant setup, no code required.

PolicyLayer is an MCP gateway: every tool call is checked against your rule before it reaches SAP Ariba MCP Server, so you can run agents against it safely.

FAQ

Questions about ariba_contract_compliance_update_request

What does the ariba_contract_compliance_update_request tool do? +

PATCH /contractRequests/{contractRequestId}. 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.

How do I enforce a policy on ariba_contract_compliance_update_request? +

Register the SAP Ariba MCP Server MCP server in PolicyLayer and add a rule for ariba_contract_compliance_update_request: 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.

What risk level is ariba_contract_compliance_update_request? +

ariba_contract_compliance_update_request is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.

Can I rate-limit ariba_contract_compliance_update_request? +

Yes. Add a rate_limit block to the ariba_contract_compliance_update_request 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.

How do I block ariba_contract_compliance_update_request completely? +

Set action: deny in the PolicyLayer policy for ariba_contract_compliance_update_request. 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.

What MCP server provides ariba_contract_compliance_update_request? +

ariba_contract_compliance_update_request 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.