List all available dashboards in Redash
AI agents call list_dashboards to retrieve information from Redash MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool queries and returns a list of existing dashboards. It performs a read-only operation that retrieves information about dashboards without modifying, deleting, or executing any data transformations. There are no side effects beyond returning information to the user. The blast radius of misuse is minimal—an AI agent could learn what dashboards exist, but cannot modify, delete, or execute them.
From the tool's definition Tool name is 'list_dashboards' and description states 'List all available dashboards in Redash' - a retrieval operation with no modification or execution of queries.
Attacks that exploit this kind of access
List all available dashboards in Redash. It is categorised as a Read tool in the Redash MCP Server MCP Server, which means it retrieves data without modifying state.
Register the Redash MCP Server MCP server in PolicyLayer and add a rule for list_dashboards: 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 Redash MCP Server. Nothing to install.
list_dashboards 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 list_dashboards 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 list_dashboards. 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.
list_dashboards is provided by the Redash MCP Server MCP server (jagadeesh52423/redash-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 →