AI agents invoke ovh_request to trigger actions in Ovh. What it does depends on the arguments the agent supplies, and its effects often reach beyond the immediate call — builds kicked off, notifications sent, workflows started.
This tool appears to be a generic OVH API request tool with no constraints on the type of request (GET, POST, PUT, DELETE, etc.) or the endpoint targeted. It could be used to read data, modify resources, delete infrastructure, trigger financial transactions (orders, payments), or any other OVH API operation.
From the tool's definition "Make a request to OVH API" - the tool name 'ovh_request' and description indicate it can make arbitrary requests to the OVH API without specifying any restriction on HTTP method or endpoint
Attacks that exploit this kind of access
Make a request to OVH API. It is categorised as a Execute tool in the Ovh MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
Register the Ovh MCP server in PolicyLayer and add a rule for ovh_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 Ovh. Nothing to install.
ovh_request is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.
Yes. Add a rate_limit block to the ovh_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.
Set action: deny in the PolicyLayer policy for ovh_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.
ovh_request is provided by the Ovh MCP server (mcp-server-ovh). 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 →