AI agents call get_task to retrieve information from Vaiz MCP without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves task information by identifier without creating, modifying, or deleting any data. It has no side effects and falls squarely within the Read category. The blast radius is minimal since it only exposes existing task metadata to the user. Severity is low because unauthorized read access to task details poses limited risk compared to write, execute, or destructive operations.
From the tool's definition Tool name is 'get_task' and description states 'Get detailed information about a specific task' — a retrieval operation with no modification of data.
Attacks that exploit this kind of access
Get detailed information about a specific task by database ID or HRID (e.g.,. It is categorised as a Read tool in the Vaiz MCP MCP Server, which means it retrieves data without modifying state.
Register the Vaiz 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 Vaiz 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 Vaiz MCP server (vaizcom/vaiz-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 →