download_task
AI agents call download_task to retrieve information from PsyFlow-MCP without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
Without explicit description, classification relies on tool name semantics and context. 'Download' typically means data retrieval with no side effects on the source system. The server's stated purpose of enabling discovery and transformation of templates suggests this tool retrieves task data (likely a template or configuration) for subsequent processing by tools like 'build_task' or 'localize'.
From the tool's definition The tool name 'download_task' indicates retrieval of task data. The empty description prevents direct confirmation, but combined with sibling tools like 'list_tasks' and 'localize' (suggesting a workflow for discovering and transforming templates),…
Attacks that exploit this kind of access
download_task. It is categorised as a Read tool in the PsyFlow-MCP MCP Server, which means it retrieves data without modifying state.
Register the PsyFlow- MCP server in PolicyLayer and add a rule for download_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 PsyFlow-MCP. Nothing to install.
download_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 download_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 download_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.
download_task is provided by the PsyFlow- MCP server (taskbeacon/taskbeacon-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Every MCP server has a record like this.
Type a name, get the same breakdown: verified identity, auth posture, risk grade, capabilities, recommended policy.
Teams ship this data inside their own products. See what a licence covers →