get_render_status

Get the current status and progress of all items in the render queue.

SERVERAe SOURCE@synthetic-ai/ae-mcp

Low RISK CLASS

Category Read

Parameters 20 required

Recommended Allowedsee the rule below

Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/synthetic-ai-ae-mcp/get-render-status.md

WHAT IT DOES

What get_render_status does on Ae

AI agents call get_render_status to retrieve information from Ae without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.

Parameter	Type	Required	Description
`timeoutMs`	number	—
`projectPath`	string	—

Parameters from the server's own tool schema.

RISK

Why get_render_status is rated Low

Even though get_render_status only reads data, uncontrolled read access leaks sensitive information and racks up API costs: an agent caught in a retry loop can make thousands of calls a minute without anyone noticing.

Risk signalsBulk/mass operation — affects multiple targets

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs get_render_status safely

PolicyLayer is an MCP gateway: it sits between your AI agents and Ae, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For get_render_status, this is the rule to start with:

get_render_status Allowed

get_render_status is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "get_render_status": {}
  }
}

ALLOW ONLY THIS TOOL → Instant setup, no code required.

The button opens the PolicyLayer dashboard: create your workspace, connect Ae, apply this rule, and every get_render_status call is checked against it from then on.

FAQ

Questions about get_render_status

What does the get_render_status tool do? +

Get the current status and progress of all items in the render queue. It is categorised as a Read tool in the Ae MCP Server, which means it retrieves data without modifying state.

What parameters does get_render_status accept? +

get_render_status accepts 2 parameters: timeoutMs, projectPath. The full parameter table on this page comes from the server's own tool schema.

How do I enforce a policy on get_render_status? +

Register the Ae MCP server in PolicyLayer and add a rule for get_render_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 Ae. Nothing to install.

What risk level is get_render_status? +

get_render_status is a Read tool with low risk. Read-only tools are generally safe to allow by default.

Can I rate-limit get_render_status? +

Yes. Add a rate_limit block to the get_render_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.

How do I block get_render_status completely? +

Set action: deny in the PolicyLayer policy for get_render_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.

What MCP server provides get_render_status? +

get_render_status is provided by the Ae MCP server (@synthetic-ai/ae-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

KEEP EXPLORING

More on Ae, and thousands of servers like it.

This server

All 226 Ae tools →

Across the catalogue

get_task_status on 0rca Dojo MCP Server →get_cocktail_by_category on Cocktails RAG MCP Server →get_torrent_detail on M-Team MCP Server →aiva_get_affiliate on AIVA MCP Server → The MCP Attack Database →

Guides

Roll out MCP under one policy →Data exfiltration →MCP token cost →