Get metadata for all columns in a worksheet: column names, long names, units, comments, and axis designations.
AI agents call tool_get_column_info to retrieve information from origin-MCP without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool purely queries and returns metadata about existing data structure. It has no side effects, does not modify data, execute code, delete information, or trigger external operations. The operation is intrinsically safe for an AI agent to invoke.
From the tool's definition Tool name contains 'get' and description states 'Get metadata for all columns' — retrieves read-only information about worksheet structure (column names, long names, units, comments, axis designations) with no modification or execution of commands.
Attacks that exploit this kind of access
Get metadata for all columns in a worksheet: column names, long names, units, comments, and axis designations. It is categorised as a Read tool in the origin-MCP MCP Server, which means it retrieves data without modifying state.
Register the origin- MCP server in PolicyLayer and add a rule for tool_get_column_info: 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 origin-MCP. Nothing to install.
tool_get_column_info 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 tool_get_column_info 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 tool_get_column_info. 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.
tool_get_column_info is provided by the origin- MCP server (zhang-923-ze/origin-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 →