Low Risk

server_info

server_info

How to control server_info ↓

AI agents call server_info to retrieve information from Micu Image MCP without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.

Low Risk

The name 'server_info' strongly implies a read-only operation that retrieves metadata or status about the server. No description is provided to confirm or deny side effects, so confidence is lowered. Among the sibling tools (batch_edit, edit, generate, multi_reference), this stands out as non-creative/non-destructive. Assigning Read with low severity as it likely just returns server metadata.

From the tool's definition Tool name is 'server_info'; description is empty and uninformative.

Documented attack patterns abuse exactly the kind of access server_info gives an agent:

PolicyLayer is an MCP gateway — it sits between your AI agents and Micu Image MCP, and nothing reaches the server without passing your rules. This is the rule we recommend for server_info:

policy.json
{
  "version": "1",
  "default": "deny",
  "tools": {
    "server_info": {}
  }
}

server_info is read-only, so it stays allowed — but everything else on the server is denied unless you say otherwise.

  1. Create a free account and register Micu Image MCP — nothing to install.
  2. Add this policy — paste it, or build it visually.
  3. Point your MCP client (Claude, Cursor, anything) at your gateway URL.
CAP THIS TOOL →

Free to start. No card required.

Go deeper

What does the server_info tool do? +

server_info. It is categorised as a Read tool in the Micu Image MCP MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on server_info? +

Register the Micu Image MCP server in PolicyLayer and add a rule for 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 Micu Image MCP. Nothing to install.

What risk level is server_info? +

server_info is a Read tool with low risk. Read-only tools are generally safe to allow by default.

Can I rate-limit server_info? +

Yes. Add a rate_limit block to the 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.

How do I block server_info completely? +

Set action: deny in the PolicyLayer policy for 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.

What MCP server provides server_info? +

server_info is provided by the Micu Image MCP server (subaru486desuwa/micu-image-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

Enforce policy on every Micu Image MCP tool call.

Deterministic rules across all 5 Micu Image MCP tools. Per-identity grants. Full audit log. Live in minutes. Nothing to install.

Free to start. No card required.

5 Micu Image MCP tools catalogued and risk-classified — across an index of 42,500+ MCP servers.

// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.