Low Risk

_exec_callback

App-only: widget calls this to resolve a pending exec request.

Part of the Tldraw server.

_exec_callback is read-only, but an agent in a loop can still rack up calls and cost. PolicyLayer caps every call before it runs. Live in minutes.

SECURE TLDRAW →

Free to start. No card required.

AI agents call _exec_callback to retrieve information from Tldraw without modifying any data. This is common in research, monitoring, and reporting workflows where the agent needs context before taking action. Because read operations don't change state, they are generally safe to allow without restrictions -- but you may still want rate limits to control API costs.

Even though _exec_callback only reads data, uncontrolled read access can leak sensitive information or rack up API costs. An agent caught in a retry loop could make thousands of calls per minute. A rate limit gives you a safety net without blocking legitimate use.

Read-only tools are safe to allow by default. No rate limit needed unless you want to control costs.

policy.json
{
  "version": "1",
  "default": "deny",
  "tools": {
    "_exec_callback": {}
  }
}

See the full Tldraw policy for all 6 tools.

Get this rule live on your own Tldraw server in minutes. PolicyLayer enforces it on every call, before it runs.

ENFORCE ON MY TLDRAW →

These attack patterns abuse exactly the kind of access _exec_callback gives an agent. Each links to the full case and the policy that stops it:

Browse the full MCP Attack Database →

Every attack above starts with a tool call. PolicyLayer checks each one against your policy first, so _exec_callback only ever does what you allow.

SECURE TLDRAW →

Other read tools across the catalogue. The same approach applies to each: allow, with a rate cap to control cost.

What does the _exec_callback tool do? +

App-only: widget calls this to resolve a pending exec request.. It is categorised as a Read tool in the Tldraw MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on _exec_callback? +

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

What risk level is _exec_callback? +

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

Can I rate-limit _exec_callback? +

Yes. Add a rate_limit block to the _exec_callback 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 _exec_callback completely? +

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

_exec_callback is provided by the Tldraw MCP server (https://tldraw-mcp-app.tldraw.workers.dev/mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

Enforce policy on every Tldraw tool call.

Deterministic rules across all 6 Tldraw tools. Per-identity grants. Full audit log. Live in minutes. Nothing to install.

Free to start. No card required.

4,600+ MCP servers and 31,000+ tools scanned and risk-classified.

// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.