scheduled_task_runs_logs
Read scheduled-task-runs.logs through the Appaloft application operation catalog. Shared with CLI and HTTP/API.
This record as markdown: /tools/appaloft-mcp/scheduled-task-runs-logs.md
What scheduled_task_runs_logs does on Appaloft
AI agents call scheduled_task_runs_logs 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 | — | |
runId | string | Yes | |
cursor | string | — | |
taskId | string | — | |
resourceId | string | — |
Parameters from the server's own tool schema.
Why scheduled_task_runs_logs is rated Low
This tool queries and retrieves log information about scheduled task runs. The verb 'Read' combined with 'logs' indicates a data retrieval operation with no side effects. There is no indication of write, execute, deletion, or financial operations. The low severity reflects minimal risk if accessed inappropriately—logs are typically informational data with no destructive capabilities.
From the tool's definition Tool description explicitly states 'Read scheduled-task-runs.logs' and retrieves log data through the application operation catalog with no modification or deletion capability mentioned.
Attacks that exploit this kind of access
The rule that runs scheduled_task_runs_logs 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_logs, this is the rule to start with:
scheduled_task_runs_logs 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_logs call is checked against it from then on.
Questions about scheduled_task_runs_logs
Read scheduled-task-runs.logs 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_logs accepts 5 parameters: limit, runId, cursor, 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_logs: 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_logs 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_logs 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_logs. 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_logs 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