get_installed_applications
Get list of installed runtime applications (Node.js, Python, etc.)
This record as markdown: /tools/cbrown35-20i-mcp/get-installed-applications.md
What get_installed_applications does on 20i MCP Server
AI agents call get_installed_applications to retrieve information from 20i MCP Server without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
Why get_installed_applications is rated Low
This tool performs a read-only operation that queries the system for installed applications. It has no destructive, financial, or executable consequences. While deployed on a hosting management server, this specific tool merely enumerates what is present rather than executing code, modifying configurations, or altering data.
From the tool's definition Tool retrieves a list of installed applications without performing any modifications or side effects. The description explicitly indicates it is a 'get' operation that queries installed runtime applications.
Attacks that exploit this kind of access
The rule that runs get_installed_applications safely
PolicyLayer is an MCP gateway: it sits between your AI agents and 20i MCP Server, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For get_installed_applications, this is the rule to start with:
get_installed_applications 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 20i MCP Server, apply this rule, and every get_installed_applications call is checked against it from then on.
Questions about get_installed_applications
Get list of installed runtime applications (Node.js, Python, etc.). It is categorised as a Read tool in the 20i MCP Server MCP Server, which means it retrieves data without modifying state.
Register the 20i MCP Server MCP server in PolicyLayer and add a rule for get_installed_applications: 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 20i MCP Server. Nothing to install.
get_installed_applications 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 get_installed_applications 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 get_installed_applications. 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.
get_installed_applications is provided by the 20i MCP Server MCP server (cbrown35/20i-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on 20i MCP Server, and thousands of servers like it.
This server
Across the catalogue