AI agents invoke query_and_plotly_chart to trigger actions in StarRocks MCP Server. 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.
The tool name suggests it executes a query and generates a Plotly chart. Given the server context of direct SQL execution and the presence of sibling tools for read and write queries, this tool likely executes SQL (potentially arbitrary) and renders a visualization. The Execute category applies because it runs queries and triggers external rendering operations.
From the tool's definition Tool name 'query_and_plotly_chart' combined with sibling tools 'read_query', 'write_query', 'analyze_query' on a server described as allowing 'direct SQL execution and database exploration'
Documented attack patterns abuse exactly the kind of access query_and_plotly_chart gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and StarRocks MCP Server, and nothing reaches the server without passing your rules. This is the rule we recommend for query_and_plotly_chart:
{
"version": "1",
"default": "deny",
"tools": {
"query_and_plotly_chart": {
"limits": [
{
"counter": "query_and_plotly_chart_rate",
"window": "minute",
"max": 10,
"scope": "grant"
}
]
}
}
}query_and_plotly_chart stays usable, but rate-capped — a runaway agent can't fire it dozens of times a minute. Everything else on the server is denied unless you say otherwise.
Free to start. No card required.
query_and_plotly_chart. It is categorised as a Execute tool in the StarRocks MCP Server MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
Register the StarRocks MCP Server MCP server in PolicyLayer and add a rule for query_and_plotly_chart: 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 StarRocks MCP Server. Nothing to install.
query_and_plotly_chart 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 query_and_plotly_chart 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 query_and_plotly_chart. 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.
query_and_plotly_chart is provided by the StarRocks MCP Server MCP server (starrocks/mcp-server-starrocks). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Deterministic rules across all 6 StarRocks MCP Server tools. Per-identity grants. Full audit log. Live in minutes. Nothing to install.
Free to start. No card required.
6 StarRocks MCP Server tools catalogued and risk-classified — across an index of 42,500+ MCP servers.