AI agents call ovh_get_dedicated_servers to retrieve information from Ovh without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves information about dedicated servers from the OVH API. It is a read-only query operation that has no side effects—it does not create, modify, delete, or execute any actions. The 'get' prefix and minimal description confirm this is a simple data retrieval function. Severity is low because misuse would only expose existing infrastructure metadata without enabling further harmful actions directly.
From the tool's definition Tool name 'ovh_get_dedicated_servers' uses the 'get' verb and description states 'Get dedicated servers', indicating a retrieval operation with no modification or deletion of data.
Attacks that exploit this kind of access
Get dedicated servers. It is categorised as a Read tool in the Ovh MCP Server, which means it retrieves data without modifying state.
Register the Ovh MCP server in PolicyLayer and add a rule for ovh_get_dedicated_servers: 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_get_dedicated_servers 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 ovh_get_dedicated_servers 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_get_dedicated_servers. 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_get_dedicated_servers 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 →