读取工程概览，包括布局、地图框、默认地图候选与数据源状态。
AI agents call inspect_project_context to retrieve information from ArcGIS Pro Bridge MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves and queries ArcGIS Pro project metadata and status information without creating, modifying, deleting, or executing operations. It is a pure information-gathering operation with no side effects on the project or underlying data. The low severity reflects minimal blast radius—an AI agent misusing this could at worst gather project information, posing no data loss or system compromise risk.
From the tool's definition Tool name is 'inspect_project_context' and description states '读取工程概览' (read project overview), including layouts, map frames, default map candidates, and data source status. The verb '读取' means 'read/retrieve' with no modification indicated.
Documented attack patterns abuse exactly the kind of access inspect_project_context gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and ArcGIS Pro Bridge MCP Server, and nothing reaches the server without passing your rules. This is the rule we recommend for inspect_project_context:
{
"version": "1",
"default": "deny",
"tools": {
"inspect_project_context": {}
}
}inspect_project_context 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.
读取工程概览，包括布局、地图框、默认地图候选与数据源状态。. It is categorised as a Read tool in the ArcGIS Pro Bridge MCP Server MCP Server, which means it retrieves data without modifying state.
Register the ArcGIS Pro Bridge MCP Server MCP server in PolicyLayer and add a rule for inspect_project_context: 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 ArcGIS Pro Bridge MCP Server. Nothing to install.
inspect_project_context 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 inspect_project_context 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 inspect_project_context. 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.
inspect_project_context is provided by the ArcGIS Pro Bridge MCP Server MCP server (sangwxx/arcgis-pro-bridge-mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Deterministic rules across all 13 ArcGIS Pro Bridge MCP Server tools. Per-identity grants. Full audit log. Live in minutes. Nothing to install.
Free to start. No card required.
13 ArcGIS Pro Bridge MCP Server tools catalogued and risk-classified — across an index of 42,500+ MCP servers.