AI agents call plane-instance-get to retrieve information from Plane without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This is a read operation that queries instance configuration. However, it retrieves sensitive administrative settings including auth configuration, which could inform an attacker about system architecture and authentication mechanisms. While the blast radius is limited to information disclosure rather than data modification or deletion, the sensitivity of admin-level configuration data warrants medium severity.
From the tool's definition Tool description states 'Get instance settings' which retrieves configuration data without modifying it. Requires admin access to read name, version, edition, domain, and auth config.
Risk signalsAdmin/system-level operation
Attacks that exploit this kind of access
Get instance settings (name, version, edition, domain, auth config). Requires admin access. It is categorised as a Read tool in the Plane MCP Server, which means it retrieves data without modifying state.
Register the Plane MCP server in PolicyLayer and add a rule for plane-instance-get: 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 Plane. Nothing to install.
plane-instance-get 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 plane-instance-get 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 plane-instance-get. 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.
plane-instance-get is provided by the Plane MCP server (philipvanlewis/plane-mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the 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 →