特定のMCPサーバーの設定を取得する。
AI agents call get_server to retrieve information from MCP Configuration Editor without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
The tool retrieves existing MCP server configuration data without modifying, deleting, or executing anything. While the broader server includes write/destructive operations (add_server, remove_server, update_server), this specific tool only performs data retrieval. The security risk is low—misuse would only expose configuration details, not cause damage or unauthorized changes.
From the tool's definition Tool name 'get_server' and description indicating it 'retrieves/obtains the configuration of a specific MCP server' (Japanese: 特定のMCPサーバーの設定を取得する translates to 'get/retrieve the configuration of a specific MCP server').
Attacks that exploit this kind of access
特定のMCPサーバーの設定を取得する。. It is categorised as a Read tool in the MCP Configuration Editor MCP Server, which means it retrieves data without modifying state.
Register the MCP Configuration Editor MCP server in PolicyLayer and add a rule for get_server: 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 MCP Configuration Editor. Nothing to install.
get_server 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_server 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_server. 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_server is provided by the MCP Configuration Editor MCP server (r3-yamauchi/mcp-conf-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 →