socrata.datasets.detail
Get full metadata and column schema for one dataset on a specific Socrata portal — description, attribution, tags, view/download counts, last data update time, and the full column list (name, field name, data type, description). Use socrata.dataset_search first to find a domain + dataset_id. Data...
This record as markdown: /tools/io-github-whiteknightonhorse-apibase/socrata.datasets.detail.md
What socrata.datasets.detail does on Apibase
AI agents use socrata.datasets.detail to create or update resources in Apibase, usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Apibase environment.
| Parameter | Type | Required | Description |
|---|---|---|---|
domain | string | Yes | Socrata portal hostname, e.g. "data.cityofnewyork.us" (from socrata.dataset_search results) |
dataset_id | string | Yes | Socrata dataset 4x4 identifier, e.g. "erm2-nwe9" (from socrata.dataset_search results) |
Parameters from the server's own tool schema.
Why socrata.datasets.detail is rated Medium
An AI agent can call socrata.datasets.detail faster than any human can review: one bad instruction and it creates or modifies resources in Apibase by the hundred, each call as confident as the last.
Attacks that exploit this kind of access
The rule that runs socrata.datasets.detail safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Apibase, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For socrata.datasets.detail, this is the rule to start with:
socrata.datasets.detail stays usable, but capped: an agent stuck in a loop can't make hundreds of changes a minute. Everything else on the server is denied unless you say otherwise.
The button opens the PolicyLayer dashboard: create your workspace, connect Apibase, apply this rule, and every socrata.datasets.detail call is checked against it from then on.
Questions about socrata.datasets.detail
Get full metadata and column schema for one dataset on a specific Socrata portal — description, attribution, tags, view/download counts, last data update time, and the full column list (name, field name, data type, description). Use socrata.dataset_search first to find a domain + dataset_id. Data: per-portal Socrata views API (e.g. data.cityofnewyork.us), no auth required. It is categorised as a Write tool in the Apibase MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
socrata.datasets.detail accepts 2 parameters: domain, dataset_id. Required: domain, dataset_id. The full parameter table on this page comes from the server's own tool schema.
Register the Apibase MCP server in PolicyLayer and add a rule for socrata.datasets.detail: 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 Apibase. Nothing to install.
socrata.datasets.detail is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.
Yes. Add a rate_limit block to the socrata.datasets.detail 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 socrata.datasets.detail. 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.
socrata.datasets.detail is provided by the Apibase MCP server (apibase-mcp-client). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Apibase, and thousands of servers like it.
This server
Across the catalogue