Return the path to the config file and the full current configuration.
AI agents call get_config_info to retrieve information from Agentic Bits Claude Plugin without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves and returns configuration data without modifying, deleting, or executing any operations. It is a straightforward read operation with minimal blast radius even if misused by an AI agent, as it only exposes existing configuration metadata.
From the tool's definition Tool name is 'get_config_info' and description states it 'Return[s] the path to the config file and the full current configuration' — purely retrieval with no modification or side effects.
Attacks that exploit this kind of access
Return the path to the config file and the full current configuration. It is categorised as a Read tool in the Agentic Bits Claude Plugin MCP Server, which means it retrieves data without modifying state.
Register the Agentic Bits Claude Plugin MCP server in PolicyLayer and add a rule for get_config_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 Agentic Bits Claude Plugin. Nothing to install.
get_config_info is a Read tool with low risk. Read-only tools are generally safe to allow by default.
Yes. Add a rate_limit block to the get_config_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.
Set action: deny in the PolicyLayer policy for get_config_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.
get_config_info is provided by the Agentic Bits Claude Plugin MCP server (onesmartguy/agentic-bits-claude-plugin). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Every MCP server has a record like this.
Type a name, get the same breakdown: verified identity, auth posture, risk grade, capabilities, recommended policy.
Teams ship this data inside their own products. See what a licence covers →