AI agents call generate_dashboard as a supporting operation in Kestra Python MCP Server workflows.
With an empty description, I can only infer from the name. 'Generate dashboard' suggests creating or rendering a dashboard view, which could be a Read (rendering/querying data) or Write (creating a dashboard artifact) operation. Given the ambiguity and lack of description, I classify it as Other with low confidence. It does not clearly indicate destructive, financial, or execute-level risk based on the name alone.
From the tool's definition Tool name is 'generate_dashboard' but the description is empty or uninformative, providing no detail about what this tool does.
Documented attack patterns abuse exactly the kind of access generate_dashboard gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Kestra Python MCP Server, and nothing reaches the server without passing your rules. This is the rule we recommend for generate_dashboard:
{
"version": "1",
"default": "deny",
"tools": {
"generate_dashboard": {
"limits": [
{
"counter": "generate_dashboard_rate",
"window": "minute",
"max": 60,
"scope": "grant"
}
]
}
}
}generate_dashboard gets a rate cap, and everything else on the server is denied unless you say otherwise.
Free to start. No card required.
generate_dashboard. It is categorised as a Other tool in the Kestra Python MCP Server MCP Server, which means it performs auxiliary operations.
Register the Kestra Python MCP Server MCP server in PolicyLayer and add a rule for generate_dashboard: 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 Kestra Python MCP Server. Nothing to install.
generate_dashboard is a Other tool with low risk. Read-only tools are generally safe to allow by default.
Yes. Add a rate_limit block to the generate_dashboard 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 generate_dashboard. 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.
generate_dashboard is provided by the Kestra Python MCP Server MCP server (kestra-io/mcp-server-python). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from Kestra Python MCP Server, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.
Free to start. No card required.
39 Kestra Python MCP Server tools catalogued and risk-classified — across an index of 43,000+ MCP servers.