get_app
Get detailed info about a published app including bandwidth usage
This record as markdown: /tools/deloc-mcp/get-app.md
What get_app does on Deloc
AI agents call get_app to retrieve information from Deloc without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
Why get_app is rated Low
This is a read-only operation that queries app metadata and usage statistics. There are no side effects, no code execution, and no data modification. It poses minimal risk as it only returns informational data about existing published apps.
From the tool's definition Tool name 'get_app' with description 'Get detailed info about a published app including bandwidth usage' retrieves app information and metrics without modifying or executing anything.
Attacks that exploit this kind of access
The rule that runs get_app safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Deloc, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For get_app, this is the rule to start with:
get_app 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 Deloc, apply this rule, and every get_app call is checked against it from then on.
Questions about get_app
Get detailed info about a published app including bandwidth usage. It is categorised as a Read tool in the Deloc MCP Server, which means it retrieves data without modifying state.
Register the Deloc MCP server in PolicyLayer and add a rule for get_app: 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 Deloc. Nothing to install.
get_app 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_app 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_app. 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_app is provided by the Deloc MCP server (delocdev/deloc-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Deloc, and thousands of servers like it.
This server
Across the catalogue