get-agent-self

THE RISK

Low Risk

Why get-agent-self needs a policy

This tool retrieves metadata about the agent (hostname, version, configuration, etc.) with no capability to modify, delete, or execute operations. It is a straightforward read operation with minimal security impact. The low severity reflects that agent self-information is typically non-sensitive operational metadata.

From the tool's definition Tool name 'get-agent-self' and description 'Get agent self information' indicate a retrieval operation that returns information about the Consul agent itself without modification or side effects.

Documented attack patterns abuse exactly the kind of access get-agent-self gives an agent:

POLICY

How to control get-agent-self

PolicyLayer is an MCP gateway — it sits between your AI agents and Consul MCP Server, and nothing reaches the server without passing your rules. This is the rule we recommend for get-agent-self:

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "get-agent-self": {}
  }
}

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

Create a free account and register Consul MCP Server — nothing to install.
Add this policy — paste it, or build it visually.
Point your MCP client (Claude, Cursor, anything) at your gateway URL.

CAP THIS TOOL →

Free to start. No card required.

EXPLORE

Related tools and policies

More Consul MCP Server tools

Destructive delete-kv Delete a key from the KV store Destructive destroy-session Destroy a session in Consul Destructive deregister-health-check Deregister a health check from Consul Destructive deregister-service Deregister a service from Consul Execute execute-prepared-query Execute a prepared query Execute fire-event Fire a new event Execute reload-agent Reload agent configuration Write create-prepared-query Create a new prepared query

All 25 Consul MCP Server tools →

Read tools on other servers

M-Team MCP Server get_torrent_detail YouTube MCP Server search_channel Android Forensics ADB MCP Server parse_browser_history 0xarchive web3_challenge

Go deeper

The MCP Attack Database → Documented attack patterns against MCP deployments — and the policies that stop them.
Data exfiltration → How read access becomes an exfiltration channel when chained with untrusted content.
MCP token cost → What connecting this server costs in context-window tokens on every request.
Rate Limiting MCP Tool Calls: A Practical Guide →
MCP Security: Why Prompt Guardrails Aren't Enough →

FAQ

Questions about get-agent-self

What does the get-agent-self tool do? +

Get agent self information. It is categorised as a Read tool in the Consul MCP Server MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on get-agent-self? +

Register the Consul MCP Server MCP server in PolicyLayer and add a rule for get-agent-self: 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 Consul MCP Server. Nothing to install.

What risk level is get-agent-self? +

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

Can I rate-limit get-agent-self? +

Yes. Add a rate_limit block to the get-agent-self 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-agent-self completely? +

Set action: deny in the PolicyLayer policy for get-agent-self. 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-agent-self? +

get-agent-self is provided by the Consul MCP Server MCP server (kocierik/consul-mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

Enforce policy on every Consul MCP Server tool call.

Start from Consul MCP Server, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.

CHECK YOUR STACK →