Turn-start reflex. Call at the start of a turn (not session) to receive a compact priors
AI agents invoke prior_for_turn to trigger actions in Sovereign Stack. 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.
prior_for_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.
Attacks that exploit this kind of access
Turn-start reflex. Call at the start of a turn (not session) to receive a compact priors. It is categorised as a Execute tool in the Sovereign Stack MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
Register the Sovereign Stack MCP server in PolicyLayer and add a rule for prior_for_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 Sovereign Stack. Nothing to install.
prior_for_turn is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.
Yes. Add a rate_limit block to the prior_for_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.
Set action: deny in the PolicyLayer policy for prior_for_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.
prior_for_turn is provided by the Sovereign Stack MCP server (templetwo/sovereign-stack). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.