list_goal_metrics
List what a goal can measure, to build create_goal input: templates (the deals_created and invoice_revenue presets and ready custom definitions) and, for each source object, its measures with their unit (count, money or number), the date fields that place a record in a month, the default date fie...
This record as markdown: /tools/sankahq-sanka-mcp/list-goal-metrics.md
What list_goal_metrics does on Sanka MCP Server
AI agents call list_goal_metrics to retrieve information from Sanka MCP Server without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
Why list_goal_metrics is rated Low
Even though list_goal_metrics only reads data, uncontrolled read access leaks sensitive information and racks up API costs: an agent caught in a retry loop can make thousands of calls a minute without anyone noticing.
Attacks that exploit this kind of access
The rule that runs list_goal_metrics safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Sanka MCP Server, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For list_goal_metrics, this is the rule to start with:
list_goal_metrics is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.
The button opens the PolicyLayer dashboard: create your workspace, connect Sanka MCP Server, apply this rule, and every list_goal_metrics call is checked against it from then on.
Questions about list_goal_metrics
List what a goal can measure, to build create_goal input: templates (the deals_created and invoice_revenue presets and ready custom definitions) and, for each source object, its measures with their unit (count, money or number), the date fields that place a record in a month, the default date field, whether records have an owner (goals on objects without one are company-only) and filter_object_type, the object whose fields definition.filters can use. It is categorised as a Read tool in the Sanka MCP Server MCP Server, which means it retrieves data without modifying state.
Register the Sanka MCP Server MCP server in PolicyLayer and add a rule for list_goal_metrics: 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 Sanka MCP Server. Nothing to install.
list_goal_metrics 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_goal_metrics 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_goal_metrics. 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_goal_metrics is provided by the Sanka MCP Server MCP server (sankahq/sanka-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Sanka MCP Server, and thousands of servers like it.
This server
Across the catalogue