This record as markdown: /tools/io-github-devopam-mcpg/audit-settings.md
What audit_settings does on Mcpg
AI agents call audit_settings to retrieve information from Mcpg without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
Why audit_settings is rated Low
Based on the name alone, 'audit_settings' appears to query or retrieve audit configuration data rather than modify, execute, or delete. The empty description lowers confidence, but naming convention and the audit/settings nature of similar tools in production PostgreSQL systems typically involves read-only inspection.
From the tool's definition Tool name 'audit_settings' suggests retrieval or inspection of audit configuration; no description provided to confirm capabilities.
Attacks that exploit this kind of access
The rule that runs audit_settings safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Mcpg, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For audit_settings, this is the rule to start with:
audit_settings is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.
The button opens the PolicyLayer dashboard: create your workspace, connect Mcpg, apply this rule, and every audit_settings call is checked against it from then on.
Questions about audit_settings
audit_settings is a read tool on the Mcpg MCP server. It is categorised as a Read tool in the Mcpg MCP Server, which means it retrieves data without modifying state.
Register the Mcpg MCP server in PolicyLayer and add a rule for audit_settings: 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 Mcpg. Nothing to install.
audit_settings 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 audit_settings 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 audit_settings. 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.
audit_settings is provided by the Mcpg MCP server (pypi:mcpg). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Mcpg, and thousands of servers like it.
This server
Across the catalogue