get_app_info

THE RISK

Low Risk

Why get_app_info needs a policy

This is a simple informational query that retrieves and returns data about the application's capabilities. It performs no modifications, executions, deletions, or financial operations. The read-only nature and lack of any state-changing behavior places it firmly in the Read category with low severity, as misuse would only expose application documentation or capabilities information.

From the tool's definition Tool name 'get_app_info' and description 'Get information about what this app does and its capabilities' indicate retrieval of metadata/informational data with no side effects.

Documented attack patterns abuse exactly the kind of access get_app_info gives an agent:

POLICY

How to control get_app_info

PolicyLayer is an MCP gateway — it sits between your AI agents and Pane, and nothing reaches the server without passing your rules. This is the rule we recommend for get_app_info:

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "get_app_info": {}
  }
}

get_app_info is read-only, so it stays allowed — but everything else on the server is denied unless you say otherwise.

Create a free account and register Pane — nothing to install.
Add this policy — paste it, or build it visually.
Point your MCP client (Claude, Cursor, anything) at your gateway URL.

CAP THIS TOOL →

Free to start. No card required.

EXPLORE

Related tools and policies

More Pane tools

Destructive clear_user_context Clear all stored user context values. Resets the persistent store to empty. Destructive reset Reset the display to initial state (cancels pending input) Execute execute_action Execute an action to change the app state. Must be one of the available actions from get_c Execute toggle_sidebar Toggle the sidebar visibility Write append Append content to the current display Write show_input_form Display an input form to the user and request their input. Returns immediately - use get_u Write show_multi_form Display a multi-field form to collect multiple inputs at once. All field values are stored Write undo Undo the last change

All 15 Pane tools →

Read tools on other servers

M-Team MCP Server get_torrent_detail YouTube MCP Server search_channel Android Forensics ADB MCP Server parse_browser_history 0xarchive web3_challenge

Go deeper

The MCP Attack Database → Documented attack patterns against MCP deployments — and the policies that stop them.
Data exfiltration → How read access becomes an exfiltration channel when chained with untrusted content.
MCP token cost → What connecting this server costs in context-window tokens on every request.
Rate Limiting MCP Tool Calls: A Practical Guide →
MCP Security: Why Prompt Guardrails Aren't Enough →

FAQ

Questions about get_app_info

What does the get_app_info tool do? +

Get information about what this app does and its capabilities. It is categorised as a Read tool in the Pane MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on get_app_info? +

Register the Pane MCP server in PolicyLayer and add a rule for get_app_info: 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 Pane. Nothing to install.

What risk level is get_app_info? +

get_app_info is a Read tool with low risk. Read-only tools are generally safe to allow by default.

Can I rate-limit get_app_info? +

Yes. Add a rate_limit block to the get_app_info 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.

How do I block get_app_info completely? +

Set action: deny in the PolicyLayer policy for get_app_info. 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.

What MCP server provides get_app_info? +

get_app_info is provided by the Pane MCP server (zabaca/pane). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

Enforce policy on every Pane tool call.

Start from Pane, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.

CHECK YOUR STACK →