get_config

THE RISK

Low Risk

Why get_config needs a policy

This tool reads and retrieves configuration data from a JSON file. It has no side effects, does not modify data, execute code, delete resources, or move money. It is a simple read operation that queries static configuration, making it a Read category risk with low severity.

From the tool's definition Tool name 'get_config' and description 'Get the complete configuration from config.json file' indicate a retrieval operation with no modification or execution of external commands.

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

POLICY

How to control get_config

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

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "get_config": {}
  }
}

get_config 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 Agent Knowledge MCP — 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 Agent Knowledge MCP tools

Destructive delete_document Delete a document from Elasticsearch index by document ID Destructive delete_index Delete an Elasticsearch index and all its documents permanently Destructive delete_index_metadata Delete metadata documentation for an Elasticsearch index Destructive reset_config Reset config.json to defaults from config.default.json (manual reset - overwrites current Execute reload_config Reload configuration from config.json file and reinitialize all components with updated se Execute server_upgrade Upgrade this MCP server when installed via uvx with automatic configuration backup and res Execute setup_elasticsearch Auto-setup Elasticsearch using Docker with optional Kibana and force recreate options Write batch_index_directory Batch index all documents from a directory into Elasticsearch with AI-enhanced metadata ge

All 27 Agent Knowledge MCP 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_config

What does the get_config tool do? +

Get the complete configuration from config.json file with formatted display. It is categorised as a Read tool in the Agent Knowledge MCP MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on get_config? +

Register the Agent Knowledge MCP server in PolicyLayer and add a rule for get_config: 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 Agent Knowledge MCP. Nothing to install.

What risk level is get_config? +

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

Can I rate-limit get_config? +

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

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

get_config is provided by the Agent Knowledge MCP server (itshare4u/agentknowledgemcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

Enforce policy on every Agent Knowledge MCP tool call.

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

CHECK YOUR STACK →