Session bootstrap: returns Telora connection state in a single payload (connected URL, organization, product, active focus + role, pending delivery counts). Used by the SessionStart hook to surface state at chat open. Optional productId; auto-resolved when the organization has a single product. N...
Risk signalsAdmin/system-level operation
Part of the Mcp Products server.
Free to start. No card required.
AI agents invoke telora_session_state to trigger processes or run actions in Mcp Products. Execute operations can have side effects beyond the immediate call -- triggering builds, sending notifications, or starting workflows. Rate limits and argument validation are essential to prevent runaway execution.
telora_session_state can trigger processes with real-world consequences. An uncontrolled agent might start dozens of builds, send mass notifications, or kick off expensive compute jobs. PolicyLayer enforces rate limits and validates arguments to keep execution within safe bounds.
Execute tools trigger processes. Rate-limit and validate arguments to prevent unintended side effects.
{
"version": "1",
"default": "deny",
"tools": {
"telora_session_state": {
"limits": [
{
"counter": "telora_session_state_rate",
"window": "minute",
"max": 10,
"scope": "grant"
}
]
}
}
}See the full Mcp Products policy for all 14 tools.
These attack patterns abuse exactly the kind of access telora_session_state gives an agent. Each links to the full case and the policy that stops it:
Other execute tools across the catalogue. The same approach applies to each: rate-limit and validate the arguments.
Session bootstrap: returns Telora connection state in a single payload (connected URL, organization, product, active focus + role, pending delivery counts). Used by the SessionStart hook to surface state at chat open. Optional productId; auto-resolved when the organization has a single product. NOTE: branch state (commits ahead of integration) is NOT included in this response -- the server has no git access. For branch state, run telora-daemon session-state --json in the repo root.. It is categorised as a Execute tool in the Mcp Products MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
Register the Mcp Products MCP server in PolicyLayer and add a rule for telora_session_state: 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 Mcp Products. Nothing to install.
telora_session_state 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 telora_session_state 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 telora_session_state. 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.
telora_session_state is provided by the Mcp Products MCP server (@telora/mcp-products). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Deterministic rules across all 14 Mcp Products 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.