scheduled_task_runs_show
Read scheduled-task-runs.show through the Appaloft application operation catalog. Shared with CLI and HTTP/API.
This record as markdown: /tools/appaloft-mcp/scheduled-task-runs-show.md
What scheduled_task_runs_show does on Appaloft
AI agents call scheduled_task_runs_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 |
|---|---|---|---|
runId | string | Yes | |
taskId | string | — | |
resourceId | string | — |
Parameters from the server's own tool schema.
Why scheduled_task_runs_show is rated Low
This tool retrieves and displays information about scheduled task runs. It has no side effects—it queries existing data without creating, modifying, deleting, or executing operations. The explicit 'Read' prefix in the description and the 'show' suffix both confirm this is a read-only operation with minimal risk.
From the tool's definition Tool name contains 'show' and description explicitly states 'Read scheduled-task-runs.show'. The verb 'show' indicates retrieval/display of information without modification.
Attacks that exploit this kind of access
The rule that runs scheduled_task_runs_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 scheduled_task_runs_show, this is the rule to start with:
scheduled_task_runs_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 scheduled_task_runs_show call is checked against it from then on.
Questions about scheduled_task_runs_show
Read scheduled-task-runs.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.
scheduled_task_runs_show accepts 3 parameters: runId, taskId, resourceId. Required: runId. 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 scheduled_task_runs_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.
scheduled_task_runs_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 scheduled_task_runs_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 scheduled_task_runs_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.
scheduled_task_runs_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