Low Risk

column_data

Distinct values in a column.

Part of the Data Ny server.

column_data is read-only, but an agent in a loop can still rack up calls and cost. PolicyLayer caps every call before it runs. Live in minutes.

SECURE DATA NY →

Free to start. No card required.

AI agents call column_data to retrieve information from Data Ny without modifying any data. This is common in research, monitoring, and reporting workflows where the agent needs context before taking action. Because read operations don't change state, they are generally safe to allow without restrictions -- but you may still want rate limits to control API costs.

Even though column_data only reads data, uncontrolled read access can leak sensitive information or rack up API costs. An agent caught in a retry loop could make thousands of calls per minute. A rate limit gives you a safety net without blocking legitimate use.

Read-only tools are safe to allow by default. No rate limit needed unless you want to control costs.

policy.json
{
  "version": "1",
  "default": "deny",
  "tools": {
    "column_data": {}
  }
}

See the full Data Ny policy for all 24 tools.

Get this rule live on your own Data Ny server in minutes. PolicyLayer enforces it on every call, before it runs.

ENFORCE ON MY DATA NY →

View all 24 tools →

These attack patterns abuse exactly the kind of access column_data gives an agent. Each links to the full case and the policy that stops it:

Browse the full MCP Attack Database →

Every attack above starts with a tool call. PolicyLayer checks each one against your policy first, so column_data only ever does what you allow.

SECURE DATA NY →

Other read tools across the catalogue. The same approach applies to each: allow, with a rate cap to control cost.

What does the column_data tool do? +

Distinct values in a column.. It is categorised as a Read tool in the Data Ny MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on column_data? +

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

What risk level is column_data? +

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

Can I rate-limit column_data? +

Yes. Add a rate_limit block to the column_data 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 column_data completely? +

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

column_data is provided by the Data Ny MCP server (https://gateway.pipeworx.io/data-ny/mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

Enforce policy on every Data Ny tool call.

Deterministic rules across all 24 Data Ny tools. Per-identity grants. Full audit log. Live in minutes. Nothing to install.

Free to start. No card required.

4,600+ MCP servers and 31,000+ tools scanned and risk-classified.

// GET IN TOUCH

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

Message sent.

We'll get back to you soon.