audit_config
Get the current audit configuration including retention and quota settings.
This record as markdown: /tools/nasbridge/audit-config.md
What audit_config does on Nasbridge
AI agents call audit_config to retrieve information from Nasbridge without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
Why audit_config is rated Low
This tool queries and retrieves existing audit configuration data from the TrueNAS system. It has no side effects, creates no resources, executes no commands, and modifies nothing. The blast radius of misuse is minimal—an agent could at most learn about audit settings but cannot impact system state or security posture through retrieval alone.
From the tool's definition Tool name 'audit_config' with description 'Get the current audit configuration including retention and quota settings' indicates a retrieval operation.
Attacks that exploit this kind of access
The rule that runs audit_config safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Nasbridge, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For audit_config, this is the rule to start with:
audit_config 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 Nasbridge, apply this rule, and every audit_config call is checked against it from then on.
Questions about audit_config
Get the current audit configuration including retention and quota settings. It is categorised as a Read tool in the Nasbridge MCP Server, which means it retrieves data without modifying state.
Register the Nasbridge MCP server in PolicyLayer and add a rule for audit_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 Nasbridge. Nothing to install.
audit_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 audit_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 audit_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.
audit_config is provided by the Nasbridge MCP server (maverick0628/nasbridge). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Nasbridge, and thousands of servers like it.
This server
Across the catalogue