end_turn

End the OpenTelemetry trace for an agent turn. Call after completing your response.

Server Cursor Otel smith/cursor-otel
Category Execute
Risk class High
Parameters 00 required

What end_turn does on Cursor Otel

AI agents invoke end_turn to trigger actions in Cursor Otel. What it does depends on the arguments the agent supplies, and its effects often reach beyond the immediate call — builds kicked off, notifications sent, workflows started.

Why end_turn needs a policy

end_turn triggers real processes with real consequences. An agent gone sideways doesn't fire it once — it starts dozens of builds, sends mass notifications, or burns through compute before anyone looks up.

Questions about end_turn

What does the end_turn tool do? +

End the OpenTelemetry trace for an agent turn. Call after completing your response. It is categorised as a Execute tool in the Cursor Otel MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.

How do I enforce a policy on end_turn? +

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

What risk level is end_turn? +

end_turn is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.

Can I rate-limit end_turn? +

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

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

end_turn is provided by the Cursor Otel MCP server (smith/cursor-otel). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

// LOOK UP ANOTHER 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 →

// GET IN TOUCH

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

Message sent.

We'll get back to you soon.