deployments_stale_attempts
Read deployments.stale-attempts through the Appaloft application operation catalog. Shared with CLI and HTTP/API.
This record as markdown: /tools/appaloft-mcp/deployments-stale-attempts.md
What deployments_stale_attempts does on Appaloft
AI agents call deployments_stale_attempts 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 |
|---|---|---|---|
limit | integer | — | |
projectId | string | — | |
resourceId | string | — | |
staleAfterSeconds | integer | — |
Parameters from the server's own tool schema.
Why deployments_stale_attempts is rated Low
This tool retrieves information about stale deployment attempts from the Appaloft application catalog. There are no side effects, modifications, deletions, code execution, or financial implications. The severity is low because reading deployment metadata poses minimal risk—it is informational in nature and does not enable harmful actions by itself.
From the tool's definition Tool description states 'Read deployments.stale-attempts' and explicitly categorizes it as a read operation. The phrasing 'Read [resource]' directly indicates data retrieval without modification.
Attacks that exploit this kind of access
The rule that runs deployments_stale_attempts 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 deployments_stale_attempts, this is the rule to start with:
deployments_stale_attempts 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 deployments_stale_attempts call is checked against it from then on.
Questions about deployments_stale_attempts
Read deployments.stale-attempts 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.
deployments_stale_attempts accepts 4 parameters: limit, projectId, resourceId, staleAfterSeconds. 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 deployments_stale_attempts: 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.
deployments_stale_attempts 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 deployments_stale_attempts 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 deployments_stale_attempts. 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.
deployments_stale_attempts 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