get_gimbal_position

Get current camera gimbal position (pan, tilt, zoom) with human-readable directions

Server OBSBOT Camera MCP Server radar105/obsbot-camera-mcp
Category Read
Risk class Low
Parameters 00 required

What get_gimbal_position does on OBSBOT Camera MCP Server

AI agents call get_gimbal_position to retrieve information from OBSBOT Camera MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.

Why get_gimbal_position needs a policy

This tool only retrieves the current position of the camera gimbal (pan, tilt, zoom values). It is a passive query that does not create, modify, delete, or execute any operations. The human-readable directions are simply formatting of the returned position data. This is a straightforward read/query operation with minimal security risk.

From the tool's definition Tool name 'get_gimbal_position' and description 'Get current camera gimbal position' indicate a query operation that retrieves state information without modifying anything. No side effects or state changes occur.

Questions about get_gimbal_position

What does the get_gimbal_position tool do? +

Get current camera gimbal position (pan, tilt, zoom) with human-readable directions. It is categorised as a Read tool in the OBSBOT Camera MCP Server MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on get_gimbal_position? +

Register the OBSBOT Camera MCP Server MCP server in PolicyLayer and add a rule for get_gimbal_position: 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 OBSBOT Camera MCP Server. Nothing to install.

What risk level is get_gimbal_position? +

get_gimbal_position is a Read tool with low risk. Read-only tools are generally safe to allow by default.

Can I rate-limit get_gimbal_position? +

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

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

get_gimbal_position is provided by the OBSBOT Camera MCP Server MCP server (radar105/obsbot-camera-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

// LOOK UP ANOTHER 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 →

// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.