resources_show
Read resources.show through the Appaloft application operation catalog. Shared with CLI and HTTP/API.
This record as markdown: /tools/appaloft-mcp/resources-show.md
What resources_show does on Appaloft
AI agents call resources_show to retrieve information from Appaloft without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
| Parameter | Type | Required | Description |
|---|---|---|---|
resourceId | string | Yes | |
includeAccessSummary | object | — | |
includeLatestDeployment | object | — | |
includeProfileDiagnostics | object | — |
Parameters from the server's own tool schema.
Why resources_show is rated Low
The tool's primary function is to retrieve and display resource information through the Appaloft application catalog. There is no indication of data modification, deletion, code execution, or financial operations. This is a straightforward read/query operation with minimal security risk if misused by an AI agent.
From the tool's definition Tool description explicitly states "Read resources.show" and "retrieves or queries data". The verb "show" and framing as a read operation confirms this is a data retrieval function without side effects.
Attacks that exploit this kind of access
The rule that runs resources_show safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Appaloft, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For resources_show, this is the rule to start with:
resources_show 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 Appaloft, apply this rule, and every resources_show call is checked against it from then on.
Questions about resources_show
Read resources.show through the Appaloft application operation catalog. Shared with CLI and HTTP/API. It is categorised as a Read tool in the Appaloft MCP Server, which means it retrieves data without modifying state.
resources_show accepts 4 parameters: resourceId, includeAccessSummary, includeLatestDeployment, includeProfileDiagnostics. Required: resourceId. The full parameter table on this page comes from the server's own tool schema.
Register the Appaloft MCP server in PolicyLayer and add a rule for resources_show: 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 Appaloft. Nothing to install.
resources_show 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 resources_show 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 resources_show. 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.
resources_show is provided by the Appaloft MCP server (@appaloft/mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Appaloft, and thousands of servers like it.
This server
Across the catalogue