Low Risk

get_admin_info

Retrieves administrative information, restricted to specific tenants and in admin tool set.

How to control get_admin_info ↓

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

Low Risk

The word 'Retrieves' explicitly indicates a read operation that queries data without modification. Although the data is restricted and sensitive (administrative information), the action itself is non-destructive. High severity reflects the sensitivity of admin data being exposed to an AI agent, even though no side effects occur—misuse could enable reconnaissance or privilege escalation planning.

From the tool's definition Tool name 'get_admin_info' and description 'Retrieves administrative information, restricted to specific tenants and in admin tool set' indicate querying/retrieval with no modification or side effects.

Risk signalsAdmin/system-level operation

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

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

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

get_admin_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 Mcp Plexus — 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 get_admin_info tool do? +

Retrieves administrative information, restricted to specific tenants and in admin tool set. It is categorised as a Read tool in the Mcp Plexus MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on get_admin_info? +

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

What risk level is get_admin_info? +

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

Can I rate-limit get_admin_info? +

Yes. Add a rate_limit block to the get_admin_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 get_admin_info completely? +

Set action: deny in the PolicyLayer policy for get_admin_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 get_admin_info? +

get_admin_info is provided by the Mcp Plexus MCP server (super-i-tech/mcp_plexus). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

Enforce policy on every Mcp Plexus tool call.

Deterministic rules across all 11 Mcp Plexus tools. Per-identity grants. Full audit log. Live in minutes. Nothing to install.

Free to start. No card required.

11 Mcp Plexus 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.