connections_show
Read connections.show through the Appaloft application operation catalog. Shared with CLI and HTTP/API.
This record as markdown: /tools/appaloft-mcp/connections-show.md
What connections_show does on Appaloft
AI agents call connections_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 |
|---|---|---|---|
connectionId | string | Yes |
Parameters from the server's own tool schema.
Why connections_show is rated Low
The tool is designed to retrieve or query connection data through the Appaloft application. The word 'Read' in the description and the 'show' suffix (a typical pattern for read-only operations) indicate this is a data retrieval function. No creation, modification, deletion, or execution of external operations is implied. The blast radius of misuse is limited to potential information disclosure about connections.
From the tool's definition Tool name is 'connections_show' and description explicitly states 'Read connections.show' — this is a retrieval operation with no modification or side effects.
Attacks that exploit this kind of access
The rule that runs connections_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 connections_show, this is the rule to start with:
connections_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 connections_show call is checked against it from then on.
Questions about connections_show
Read connections.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.
connections_show accepts 1 parameter: connectionId. Required: connectionId. 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 connections_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.
connections_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 connections_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 connections_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.
connections_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