get_viewport_camera

Get the current editor viewport camera location and rotation.

SERVERUnreal SOURCE@jjpxdev/unreal-mcp

Low RISK CLASS

Category Read

Parameters 00 required

Recommended Allowedsee the rule below

Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/jjpxdev-unreal-mcp/get-viewport-camera.md

WHAT IT DOES

What get_viewport_camera does on Unreal

AI agents call get_viewport_camera to retrieve information from Unreal without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.

RISK

Why get_viewport_camera is rated Low

This tool queries and retrieves current camera parameters (location and rotation) from the viewport without creating, modifying, or deleting any data. It is a read-only operation with no side effects, fitting the Read category. The severity is low as unauthorized access to camera state poses minimal risk.

From the tool's definition Tool name 'get_viewport_camera' and description 'Get the current editor viewport camera location and rotation' indicate retrieval of camera state with no modification or side effects.

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs get_viewport_camera safely

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

get_viewport_camera Allowed

get_viewport_camera is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "get_viewport_camera": {}
  }
}

ALLOW ONLY THIS TOOL → Instant setup, no code required.

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

FAQ

Questions about get_viewport_camera

What does the get_viewport_camera tool do? +

Get the current editor viewport camera location and rotation. It is categorised as a Read tool in the Unreal MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on get_viewport_camera? +

Register the Unreal MCP server in PolicyLayer and add a rule for get_viewport_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 Unreal. Nothing to install.

What risk level is get_viewport_camera? +

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

Can I rate-limit get_viewport_camera? +

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

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

get_viewport_camera is provided by the Unreal MCP server (@jjpxdev/unreal-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

KEEP EXPLORING

More on Unreal, and thousands of servers like it.

This server

All 127 Unreal tools →

Across the catalogue

get_cocktail_by_category on Cocktails RAG MCP Server →get_file_snippet on ACE-MCP →get_torrent_detail on M-Team MCP Server →get_customer_data on 08-AI-Business-Agent → The MCP Attack Database →

Guides

Roll out MCP under one policy →Data exfiltration →MCP token cost →