get_console_output

THE RISK

Low Risk

Why get_console_output needs a policy

This tool retrieves historical console output from Metashape's UI, functioning as a query/read operation. It does not modify state, execute code, or cause irreversible changes. The blast radius of misuse is minimal since it only exposes existing logs already generated by prior operations.

From the tool's definition Tool description states 'Read the Metashape console pane output' - a retrieval operation with no side effects.

Documented attack patterns abuse exactly the kind of access get_console_output gives an agent:

POLICY

How to control get_console_output

PolicyLayer is an MCP gateway — it sits between your AI agents and Metashape MCP Server, and nothing reaches the server without passing your rules. This is the rule we recommend for get_console_output:

policy.json

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

get_console_output is read-only, so it stays allowed — but everything else on the server is denied unless you say otherwise.

Create a free account and register Metashape MCP Server — nothing to install.
Add this policy — paste it, or build it visually.
Point your MCP client (Claude, Cursor, anything) at your gateway URL.

CAP THIS TOOL →

Free to start. No card required.

EXPLORE

Related tools and policies

More Metashape MCP Server tools

Destructive clean_model Remove model artifacts based on filtering criteria. Destructive clear_dem Remove the DEM from the active chunk to free memory. Destructive clear_depth_maps Remove depth maps from the active chunk to free memory. Destructive clear_masks Remove masks from cameras. Destructive clear_model Remove the 3D model from the active chunk to free memory. Destructive clear_orthomosaic Remove the orthomosaic from the active chunk to free memory. Destructive clear_point_cloud Remove the dense point cloud from the active chunk to free memory. Destructive clear_tiled_model Remove the tiled model from the active chunk to free memory.

All 112 Metashape MCP Server tools →

Read tools on other servers

M-Team MCP Server get_torrent_detail YouTube MCP Server search_channel Android Forensics ADB MCP Server parse_browser_history 0xarchive web3_challenge

Go deeper

The MCP Attack Database → Documented attack patterns against MCP deployments — and the policies that stop them.
Data exfiltration → How read access becomes an exfiltration channel when chained with untrusted content.
MCP token cost → What connecting this server costs in context-window tokens on every request.
Rate Limiting MCP Tool Calls: A Practical Guide →
MCP Security: Why Prompt Guardrails Aren't Enough →

FAQ

Questions about get_console_output

What does the get_console_output tool do? +

Read the Metashape console pane output. It is categorised as a Read tool in the Metashape MCP Server MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on get_console_output? +

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

What risk level is get_console_output? +

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

Can I rate-limit get_console_output? +

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

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

get_console_output is provided by the Metashape MCP Server MCP server (jenkinsm13/metashape-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

Enforce policy on every Metashape MCP Server tool call.

Start from Metashape MCP Server, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.

CHECK YOUR STACK →