List AI coding editors supported by proxy-doctor on this platform.
AI agents call supported_editors to retrieve information from Proxy Doctor without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool reads and returns a static list of supported editors. It performs no mutations, executions, deletions, or financial transactions. The operation is informational only with minimal security risk—listing supported editors cannot cause harm or side effects to the system or data.
From the tool's definition Tool name 'supported_editors' and description 'List AI coding editors supported by proxy-doctor on this platform' indicate a query/list operation that retrieves information without modifying any data.
Attacks that exploit this kind of access
List AI coding editors supported by proxy-doctor on this platform. It is categorised as a Read tool in the Proxy Doctor MCP Server, which means it retrieves data without modifying state.
Register the Proxy Doctor MCP server in PolicyLayer and add a rule for supported_editors: 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 Proxy Doctor. Nothing to install.
supported_editors 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 supported_editors 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 supported_editors. 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.
supported_editors is provided by the Proxy Doctor MCP server (Jiansen/proxy-doctor). 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 →