capture_screenshot

Get metadata about the current Studio viewport — camera position, look direction, FOV, and visible objects. Note: Pixel capture is not available in Studio plugins. This returns camera metadata for spatial reasoning. Returns: { position, lookVector, fieldOfView, viewportSize, visibleObjects[] }

Server Melo yannyhl/linkedsword-mcp
Category Read
Risk class Low
Parameters 00 required

What capture_screenshot does on Melo

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

Why capture_screenshot needs a policy

This is a pure data retrieval operation that queries the current state of the Roblox Studio viewport without modifying, executing, or destructively affecting any data. It provides spatial awareness information for an AI agent to reason about the development environment, equivalent to a 'get' or 'query' operation. No reversible writes, code execution, deletions, or financial operations are involved.

From the tool's definition Tool retrieves camera metadata (position, look direction, FOV, visible objects) from the Studio viewport with no side effects.

Questions about capture_screenshot

What does the capture_screenshot tool do? +

Get metadata about the current Studio viewport — camera position, look direction, FOV, and visible objects. Note: Pixel capture is not available in Studio plugins. This returns camera metadata for spatial reasoning. Returns: { position, lookVector, fieldOfView, viewportSize, visibleObjects[] }. It is categorised as a Read tool in the Melo MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on capture_screenshot? +

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

What risk level is capture_screenshot? +

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

Can I rate-limit capture_screenshot? +

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

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

capture_screenshot is provided by the Melo MCP server (yannyhl/linkedsword-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.