Get all custom columns and their available options.
AI agents call get_custom_column_options to retrieve information from Standard Metrics 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 retrieves metadata about custom columns and their configuration options. It performs a read-only operation on the Standard Metrics API without creating, modifying, deleting, or executing any operations. The blast radius of misuse is minimal—at worst, an agent would retrieve column metadata that is likely already accessible to authorized users.
From the tool's definition Tool name 'get_custom_column_options' and description 'Get all custom columns and their available options' indicate a retrieval operation with no modification, deletion, or execution of code.
Documented attack patterns abuse exactly the kind of access get_custom_column_options gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Standard Metrics MCP Server, and nothing reaches the server without passing your rules. This is the rule we recommend for get_custom_column_options:
{
"version": "1",
"default": "deny",
"tools": {
"get_custom_column_options": {}
}
}get_custom_column_options is read-only, so it stays allowed — but everything else on the server is denied unless you say otherwise.
Free to start. No card required.
Get all custom columns and their available options. It is categorised as a Read tool in the Standard Metrics MCP Server MCP Server, which means it retrieves data without modifying state.
Register the Standard Metrics MCP Server MCP server in PolicyLayer and add a rule for get_custom_column_options: 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 Standard Metrics MCP Server. Nothing to install.
get_custom_column_options 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 get_custom_column_options 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 get_custom_column_options. 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.
get_custom_column_options is provided by the Standard Metrics MCP Server MCP server (quaestor-technologies/smx-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from Standard Metrics 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.
19 Standard Metrics MCP Server tools catalogued and risk-classified — across an index of 43,000+ MCP servers.