AI agents call get_corridor_drift_report to retrieve information from Metashape MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
The 'get_' prefix strongly suggests this tool retrieves or queries existing data about corridor drift (a photogrammetry metric tracking positional accuracy) without modifying state. Even in a context where sibling tools perform side-effect operations (add_photos, build_contours, align_cameras), a getter typically has no side effects.
From the tool's definition Tool name 'get_corridor_drift_report' uses 'get' prefix, indicating data retrieval. The empty description prevents full certainty, but the naming pattern is consistent with read operations on a photogrammetry server.
Documented attack patterns abuse exactly the kind of access get_corridor_drift_report gives an agent:
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_corridor_drift_report:
{
"version": "1",
"default": "deny",
"tools": {
"get_corridor_drift_report": {}
}
}get_corridor_drift_report is read-only, so it stays allowed — but everything else on the server is denied unless you say otherwise.
Free to start. No card required.
get_corridor_drift_report. It is categorised as a Read tool in the Metashape MCP Server MCP Server, which means it retrieves data without modifying state.
Register the Metashape MCP Server MCP server in PolicyLayer and add a rule for get_corridor_drift_report: 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.
get_corridor_drift_report is a Read tool with low risk. Read-only tools are generally safe to allow by default.
Yes. Add a rate_limit block to the get_corridor_drift_report 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.
Set action: deny in the PolicyLayer policy for get_corridor_drift_report. 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.
get_corridor_drift_report 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.
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.
Free to start. No card required.
112 Metashape MCP Server tools catalogued and risk-classified — across an index of 43,000+ MCP servers.