Read the full content of a specific task file.
AI agents call read_task to retrieve information from Cross-Project 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 and displays task file content without creating, modifying, deleting, or executing operations. It is a pure read operation on stored data, making it the lowest risk category. Severity is low because reading task metadata poses minimal security risk unless the tasks themselves contain highly sensitive information, but this is a data retrieval function with no destructive or executable capabilities.
From the tool's definition Tool name is 'read_task' and description states 'Read the full content of a specific task file.' The verb 'read' and 'read the full content' clearly indicate data retrieval with no modification or side effects.
Attacks that exploit this kind of access
Read the full content of a specific task file. It is categorised as a Read tool in the Cross-Project MCP Server MCP Server, which means it retrieves data without modifying state.
Register the Cross-Project MCP Server MCP server in PolicyLayer and add a rule for read_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 Cross-Project MCP Server. Nothing to install.
read_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 read_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 read_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.
read_task is provided by the Cross-Project MCP Server MCP server (sweetsrepo/cross-project-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 →