Fetch a single task by ID and return the same Markdown summary + raw detail structure used elsewhere. Invoke when the user wants to inspect status, next run, history, or agent instructions for one task.
AI agents call get_task to retrieve information from Schedule Task MCP without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
The tool retrieves and queries task metadata (status, next run, history, agent instructions) without side effects. It is a straightforward read operation on persisted task data, analogous to a 'get' or 'fetch' API call. No irreversible or dangerous actions are possible via this tool alone.
From the tool's definition Tool name 'get_task' and description 'Fetch a single task by ID and return the same Markdown summary + raw detail structure' indicate retrieval-only operations. No modification, deletion, or execution is mentioned.
Attacks that exploit this kind of access
Fetch a single task by ID and return the same Markdown summary + raw detail structure used elsewhere. Invoke when the user wants to inspect status, next run, history, or agent instructions for one task. It is categorised as a Read tool in the Schedule Task MCP MCP Server, which means it retrieves data without modifying state.
Register the Schedule Task MCP server in PolicyLayer and add a rule for get_task: 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 Schedule Task MCP. Nothing to install.
get_task 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 get_task 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 get_task. 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.
get_task is provided by the Schedule Task MCP server (liao1fan/schedule-task-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
get_task is one line of Schedule Task's registry record.
The record carries the whole server: verified identity, auth posture, risk grade, every tool classified, recommended policy — re-checked continuously.
Teams ship this data inside their own products. See what a licence covers →