Inspect any Meshy task by id. If it SUCCEEDED and download=True and it
AI agents call get_meshy_task_status to retrieve information from Meshy Bottube without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool performs a simple status inspection/query operation. It retrieves information about an existing task by its ID with no side effects, altering data, executing code, deleting data, or financial implications. This is a standard Read operation with low severity.
From the tool's definition Tool name 'get_meshy_task_status' and description 'Inspect any Meshy task by id' indicate it retrieves/queries the status of a task without modifying or executing anything.
Attacks that exploit this kind of access
Inspect any Meshy task by id. If it SUCCEEDED and download=True and it. It is categorised as a Read tool in the Meshy Bottube MCP Server, which means it retrieves data without modifying state.
Register the Meshy Bottube MCP server in PolicyLayer and add a rule for get_meshy_task_status: 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 Meshy Bottube. Nothing to install.
get_meshy_task_status 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_meshy_task_status 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_meshy_task_status. 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_meshy_task_status is provided by the Meshy Bottube MCP server (scottcjn/meshy-bottube-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 →