Get the specifications of a scheduled task by its ID.
AI agents call get_scheduled_task to retrieve information from PythonAnywhere MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves information about an existing scheduled task without creating, modifying, deleting, or executing anything. It is a pure read operation that queries task specifications based on an identifier. The low severity reflects minimal blast radius if misused—an AI agent could retrieve task details but cannot harm systems through retrieval alone.
From the tool's definition Tool name is 'get_scheduled_task' and description states 'Get the specifications of a scheduled task by its ID' — both indicate a retrieval operation with no modification or side effects.
Documented attack patterns abuse exactly the kind of access get_scheduled_task gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and PythonAnywhere MCP Server, and nothing reaches the server without passing your rules. This is the rule we recommend for get_scheduled_task:
{
"version": "1",
"default": "deny",
"tools": {
"get_scheduled_task": {}
}
}get_scheduled_task is read-only, so it stays allowed — but everything else on the server is denied unless you say otherwise.
Free to start. No card required.
Get the specifications of a scheduled task by its ID. It is categorised as a Read tool in the PythonAnywhere MCP Server MCP Server, which means it retrieves data without modifying state.
Register the PythonAnywhere MCP Server MCP server in PolicyLayer and add a rule for get_scheduled_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 PythonAnywhere MCP Server. Nothing to install.
get_scheduled_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_scheduled_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_scheduled_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_scheduled_task is provided by the PythonAnywhere MCP Server MCP server (pythonanywhere/pythonanywhere-mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from PythonAnywhere MCP Server, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.
Free to start. No card required.
20 PythonAnywhere MCP Server tools catalogued and risk-classified — across an index of 43,000+ MCP servers.