list_dashboard_widgets

Get all widgets configured on the user

SERVERinstantKOM MCP Server SOURCEinstantkom/mcp-server

Low RISK CLASS

Category Read

Parameters 00 required

Recommended Allowedsee the rule below

Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/instantkom-mcp-server/list-dashboard-widgets.md

WHAT IT DOES

What list_dashboard_widgets does on instantKOM MCP Server

AI agents call list_dashboard_widgets to retrieve information from instantKOM MCP Server without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.

RISK

Why list_dashboard_widgets is rated Low

This tool retrieves existing dashboard widget configuration data. It performs a query operation that returns information about the user's dashboard without creating, modifying, or deleting any data. This is a straightforward read operation with minimal security risk—the data returned is user-specific dashboard configuration, which is typically non-sensitive metadata.

From the tool's definition Tool name is 'list_dashboard_widgets' and description states 'Get all widgets configured on the user' — uses 'Get' verb indicating retrieval with no data modification or side effects.

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs list_dashboard_widgets safely

PolicyLayer is an MCP gateway: it sits between your AI agents and instantKOM MCP Server, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For list_dashboard_widgets, this is the rule to start with:

list_dashboard_widgets Allowed

list_dashboard_widgets is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "list_dashboard_widgets": {}
  }
}

ALLOW ONLY THIS TOOL → Instant setup, no code required.

The button opens the PolicyLayer dashboard: create your workspace, connect instantKOM MCP Server, apply this rule, and every list_dashboard_widgets call is checked against it from then on.

FAQ

Questions about list_dashboard_widgets

What does the list_dashboard_widgets tool do? +

Get all widgets configured on the user. It is categorised as a Read tool in the instantKOM MCP Server MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on list_dashboard_widgets? +

Register the instantKOM MCP Server MCP server in PolicyLayer and add a rule for list_dashboard_widgets: 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 instantKOM MCP Server. Nothing to install.

What risk level is list_dashboard_widgets? +

list_dashboard_widgets is a Read tool with low risk. Read-only tools are generally safe to allow by default.

Can I rate-limit list_dashboard_widgets? +

Yes. Add a rate_limit block to the list_dashboard_widgets 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.

How do I block list_dashboard_widgets completely? +

Set action: deny in the PolicyLayer policy for list_dashboard_widgets. 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.

What MCP server provides list_dashboard_widgets? +

list_dashboard_widgets is provided by the instantKOM MCP Server MCP server (instantkom/mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

KEEP EXPLORING

More on instantKOM MCP Server, and thousands of servers like it.

This server

All 245 instantKOM MCP Server tools →

Across the catalogue

aiva_list_affiliates on AIVA MCP Server →list_agents on 0rca Dojo MCP Server → The MCP Attack Database →

Guides

Roll out MCP under one policy →Data exfiltration →MCP token cost →