View MCP server configuration: instance name, Firebase project, credentials path, user config, environment variables. Use action
AI agents call pg_config to retrieve information from Planning Game without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool only retrieves configuration information without modifying, executing, or deleting any data. While it may expose sensitive information like credentials paths and environment variables, the tool itself performs no side effects—it is purely informational.
From the tool's definition Tool name and description explicitly state 'View MCP server configuration' and lists read-only operations: viewing instance name, Firebase project, credentials path, user config, and environment variables.
Attacks that exploit this kind of access
View MCP server configuration: instance name, Firebase project, credentials path, user config, environment variables. Use action. It is categorised as a Read tool in the Planning Game MCP Server, which means it retrieves data without modifying state.
Register the Planning Game MCP server in PolicyLayer and add a rule for pg_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 Planning Game. Nothing to install.
pg_config 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 pg_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.
Set action: deny in the PolicyLayer policy for pg_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.
pg_config is provided by the Planning Game MCP server (planning-game-mcp). 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 →