Генерирует Sequence-диаграмму выполнения от символа.
AI agents call flipchart_sequence_diagram to retrieve information from Booster MCP without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool reads code structure and generates visualization output (a sequence diagram). It retrieves and analyzes call execution flows from existing symbols but does not create, modify, delete, or execute arbitrary code. It is a read-only analysis and visualization tool. Low severity because diagrams are informational outputs with no side effects on the actual codebase or system.
From the tool's definition Генерирует Sequence-диаграмму выполнения от символа translates to 'Generates a sequence diagram of execution from a symbol'. It generates/visualizes diagram data from existing code symbols without modifying code or executing it.
Attacks that exploit this kind of access
Генерирует Sequence-диаграмму выполнения от символа. It is categorised as a Read tool in the Booster MCP MCP Server, which means it retrieves data without modifying state.
Register the Booster MCP server in PolicyLayer and add a rule for flipchart_sequence_diagram: 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_sequence_diagram is a Read tool with low risk. Read-only tools are generally safe to allow by default.
Yes. Add a rate_limit block to the flipchart_sequence_diagram 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_sequence_diagram. 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_sequence_diagram 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 →