This record as markdown: /tools/spranab-truenas-mcp/kerberos-config.md
What kerberos_config does on Truenas
AI agents call kerberos_config to retrieve information from Truenas without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
Why kerberos_config is rated Low
This tool retrieves Kerberos configuration settings without altering any state or data. It performs a read-only query operation. While Kerberos configuration may contain sensitive information, the tool itself only exposes data retrieval capabilities with no side effects, placing it firmly in the Read category with low severity.
From the tool's definition Tool name 'kerberos_config' with description 'Get Kerberos configuration settings' uses the verb 'Get', which indicates data retrieval without modification.
Attacks that exploit this kind of access
The rule that runs kerberos_config safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Truenas, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For kerberos_config, this is the rule to start with:
kerberos_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 Truenas, apply this rule, and every kerberos_config call is checked against it from then on.
Questions about kerberos_config
Get Kerberos configuration settings. It is categorised as a Read tool in the Truenas MCP Server, which means it retrieves data without modifying state.
Register the Truenas MCP server in PolicyLayer and add a rule for kerberos_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 Truenas. Nothing to install.
kerberos_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 kerberos_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 kerberos_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.
kerberos_config is provided by the Truenas MCP server (spranab/truenas-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Truenas, and thousands of servers like it.
This server
Across the catalogue