list-pulse-metric-definitions-from-definition-ids

Retrieves a list of specific Pulse Metric Definitions using the Tableau REST API from a list of metric definition IDs. Use this tool when a user requests information about specific Pulse Metric Definitions on the current site. Parameters: - \

Server Tableau MCP Server tableau/tableau-mcp
Category Read
Risk class Low
Parameters 00 required

What list-pulse-metric-definitions-from-definition-ids does on Tableau MCP Server

AI agents call list-pulse-metric-definitions-from-definition-ids to retrieve information from Tableau MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.

Why list-pulse-metric-definitions-from-definition-ids needs a policy

This tool simply queries and returns metric definition metadata from Tableau Pulse. It has no side effects, does not modify data, execute code, delete resources, or commit financial obligations. The blast radius of misuse is minimal—an agent could only retrieve information about metric definitions that already exist on the Tableau site. This is a straightforward Read operation.

From the tool's definition Tool performs 'Retrieves a list of specific Pulse Metric Definitions' from Tableau REST API using metric definition IDs. The action is purely data retrieval with no modification or deletion capabilities.

Questions about list-pulse-metric-definitions-from-definition-ids

What does the list-pulse-metric-definitions-from-definition-ids tool do? +

Retrieves a list of specific Pulse Metric Definitions using the Tableau REST API from a list of metric definition IDs. Use this tool when a user requests information about specific Pulse Metric Definitions on the current site. Parameters: - \. It is categorised as a Read tool in the Tableau MCP Server MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on list-pulse-metric-definitions-from-definition-ids? +

Register the Tableau MCP Server MCP server in PolicyLayer and add a rule for list-pulse-metric-definitions-from-definition-ids: 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 Tableau MCP Server. Nothing to install.

What risk level is list-pulse-metric-definitions-from-definition-ids? +

list-pulse-metric-definitions-from-definition-ids is a Read tool with low risk. Read-only tools are generally safe to allow by default.

Can I rate-limit list-pulse-metric-definitions-from-definition-ids? +

Yes. Add a rate_limit block to the list-pulse-metric-definitions-from-definition-ids 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-pulse-metric-definitions-from-definition-ids completely? +

Set action: deny in the PolicyLayer policy for list-pulse-metric-definitions-from-definition-ids. 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-pulse-metric-definitions-from-definition-ids? +

list-pulse-metric-definitions-from-definition-ids is provided by the Tableau MCP Server MCP server (tableau/tableau-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.