get_config

Returns the current LMCP configuration (api_key masked).

SERVERLocal SOURCElocal-mcp

Low RISK CLASS

Category Read

Parameters 00 required

Recommended Allowedsee the rule below

Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/com-local-mcp-local-mcp/get-config.md

WHAT IT DOES

What get_config does on Local

AI agents call get_config to retrieve information from Local without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.

RISK

Why get_config is rated Low

This tool retrieves configuration state without modifying, deleting, or executing any operations. It is purely informational. The masked API key shows appropriate security practices. No blast radius from misuse beyond information disclosure of non-sensitive config data.

From the tool's definition Tool name is 'get_config' and description states it 'Returns the current LMCP configuration'. The verb 'Returns' indicates a retrieval operation with no side effects. The note that api_key is masked further confirms this is a read-only introspection tool.

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs get_config safely

PolicyLayer is an MCP gateway: it sits between your AI agents and Local, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For get_config, this is the rule to start with:

get_config Allowed

get_config is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.

View as policy code

policy.json

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

ALLOW ONLY THIS TOOL → Instant setup, no code required.

The button opens the PolicyLayer dashboard: create your workspace, connect Local, apply this rule, and every get_config call is checked against it from then on.

FAQ

Questions about get_config

What does the get_config tool do? +

Returns the current LMCP configuration (api_key masked). It is categorised as a Read tool in the Local MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on get_config? +

Register the Local 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 Local. 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 Local MCP server (local-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

KEEP EXPLORING

More on Local, and thousands of servers like it.

This server

All 234 Local tools →

Across the catalogue

get_cocktail_by_category on Cocktails RAG MCP Server →get_torrent_detail on M-Team MCP Server →aiva_get_affiliate on AIVA MCP Server →get-chuck-categories on Jokes MCP Server → The MCP Attack Database →

Guides

Roll out MCP under one policy →Data exfiltration →MCP token cost →