app_available
List all available apps from the catalog. Returns apps that can be installed.
This record as markdown: /tools/spranab-truenas-mcp/app-available.md
What app_available does on Truenas
AI agents call app_available 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 app_available is rated Low
This tool only reads and returns information about available applications; it performs no creation, modification, deletion, execution, or financial operations. The operation is purely informational with no side effects on the TrueNAS system.
From the tool's definition Tool name 'app_available' and description 'List all available apps from the catalog. Returns apps that can be installed.' indicate a query/list operation that retrieves catalog information without modifying state.
Attacks that exploit this kind of access
The rule that runs app_available 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 app_available, this is the rule to start with:
app_available 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 app_available call is checked against it from then on.
Questions about app_available
List all available apps from the catalog. Returns apps that can be installed. 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 app_available: 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.
app_available 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 app_available 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 app_available. 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.
app_available 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