Get information about the MCP Affinity Designer server / MCP Affinity Designerサーバーの情報を取得
AI agents call get_server_info to retrieve information from MCP Affinity Designer Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool queries and returns information about the server itself—a pure read operation with no side effects, no code execution, and no data modification. It is analogous to 'get' or 'fetch' operations that retrieve metadata. Even if an AI agent misuses it, the blast radius is minimal since it only exposes read-only server information.
From the tool's definition Tool name 'get_server_info' and description 'Get information about the MCP Affinity Designer server' indicate this retrieves server metadata without modifying or executing operations on Affinity Designer documents or state.
Documented attack patterns abuse exactly the kind of access get_server_info gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and MCP Affinity Designer Server, and nothing reaches the server without passing your rules. This is the rule we recommend for get_server_info:
{
"version": "1",
"default": "deny",
"tools": {
"get_server_info": {}
}
}get_server_info 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 information about the MCP Affinity Designer server / MCP Affinity Designerサーバーの情報を取得. It is categorised as a Read tool in the MCP Affinity Designer Server MCP Server, which means it retrieves data without modifying state.
Register the MCP Affinity Designer Server MCP server in PolicyLayer and add a rule for get_server_info: 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 Affinity Designer Server. Nothing to install.
get_server_info 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_info 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_info. 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_info is provided by the MCP Affinity Designer Server MCP server (szgk/mcp-affinity-designer). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from MCP Affinity Designer 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.
28 MCP Affinity Designer Server tools catalogued and risk-classified — across an index of 43,000+ MCP servers.