rotate_camera

Rotate the camera by azimuth and elevation angles in degrees.

SERVERCLIO Adios SOURCEpypi:clio-kit

High RISK CLASS

Category Execute

Parameters 00 required

Recommended Rate-limitedsee the rule below

Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/io-github-iowarp-adios-mcp/rotate-camera.md

WHAT IT DOES

What rotate_camera does on CLIO Adios

AI agents invoke rotate_camera to trigger actions in CLIO Adios. 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.

RISK

Why rotate_camera is rated High

This tool triggers an external operation (camera rotation in a visualization context), which is an action with side effects beyond simple data retrieval. It modifies the state of a rendering/visualization session. It doesn't read, write persistent data, delete, or involve finances. Execute is the best fit as it triggers an external operation whose effect depends on arguments (azimuth and elevation angles).

From the tool's definition 'Rotate the camera by azimuth and elevation angles in degrees'

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs rotate_camera safely

PolicyLayer is an MCP gateway: it sits between your AI agents and CLIO Adios, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For rotate_camera, this is the rule to start with:

rotate_camera Rate-limited

rotate_camera stays usable, but rate-capped: a runaway agent can't fire it dozens of times a minute. Everything else on the server is denied unless you say otherwise.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "rotate_camera": {
      "limits": [
        {
          "counter": "rotate_camera_rate",
          "window": "minute",
          "max": 10,
          "scope": "grant"
        }
      ]
    }
  }
}

RATE-LIMIT THIS TOOL → Instant setup, no code required.

The button opens the PolicyLayer dashboard: create your workspace, connect CLIO Adios, apply this rule, and every rotate_camera call is checked against it from then on.

FAQ

Questions about rotate_camera

What does the rotate_camera tool do? +

Rotate the camera by azimuth and elevation angles in degrees. It is categorised as a Execute tool in the CLIO Adios MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.

How do I enforce a policy on rotate_camera? +

Register the CLIO Adios MCP server in PolicyLayer and add a rule for rotate_camera: 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 CLIO Adios. Nothing to install.

What risk level is rotate_camera? +

rotate_camera is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.

Can I rate-limit rotate_camera? +

Yes. Add a rate_limit block to the rotate_camera 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 rotate_camera completely? +

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

rotate_camera is provided by the CLIO Adios MCP server (pypi:clio-kit). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

KEEP EXPLORING

More on CLIO Adios, and thousands of servers like it.

This server

All 204 CLIO Adios tools → High-risk tools on this server →

Across the catalogue

All high-risk MCP tools → The MCP Attack Database →

Guides

Govern code and CI agents →Agent sandbox →Least privilege for MCP →