promote_session
AI agents use promote_session to create or update resources in Astria-Index — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Astria-Index environment.
Without explicit documentation, 'promote' most likely means reordering, prioritizing, or otherwise modifying session attributes—a reversible write operation. The medium severity reflects potential for unintended session reorganization affecting memory recall if misused by an agent, but no irreversible deletion or financial impact. Confidence is reduced due to the empty description.
From the tool's definition Tool name 'promote_session' suggests modifying the state or metadata of a session object. The empty description prevents precise determination, but the verb 'promote' implies a change operation rather than retrieval.
Attacks that exploit this kind of access
promote_session. It is categorised as a Write tool in the Astria-Index MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Astria-Index MCP server in PolicyLayer and add a rule for promote_session: 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 Astria-Index. Nothing to install.
promote_session is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.
Yes. Add a rate_limit block to the promote_session 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 promote_session. 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.
promote_session is provided by the Astria-Index MCP server (pl-odin/astria-plugin). 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 →