Создаёт сессию дебага для отслеживания группы символов.
AI agents use flipchart_create_session to create or update resources in Booster MCP — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Booster MCP environment.
The tool creates a new debug session, which is a Write operation—it instantiates new data structures for tracking purposes. While sessions are typically ephemeral and don't permanently alter the codebase, creating them is a Write action. Severity is low because debug sessions are read-only tracking mechanisms with no side effects on the actual codebase or system behavior.
From the tool's definition Tool description: 'Создаёт сессию дебага для отслеживания группы символов' (Creates a debug session for tracking a group of symbols). This creates a new debug session object, which is a reversible data creation action.
Attacks that exploit this kind of access
Создаёт сессию дебага для отслеживания группы символов. It is categorised as a Write tool in the Booster MCP MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Booster MCP server in PolicyLayer and add a rule for flipchart_create_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 Booster MCP. Nothing to install.
flipchart_create_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 flipchart_create_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 flipchart_create_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.
flipchart_create_session is provided by the Booster MCP server (neuroghostdev/booster_mcp). 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 →