list_schema_fields
AI agents call list_schema_fields to retrieve information from DataHub MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
The tool name suggests listing/retrieving schema field information with no modification capability. Although the description is empty (lowering confidence slightly), the server's stated purpose is data exploration and the surrounding tools are predominantly Read operations. No evidence of write, execute, destructive, or financial operations. This is a metadata retrieval operation with no side effects.
From the tool's definition Tool name 'list_schema_fields' indicates retrieval of schema field metadata. Server description emphasizes read/exploration capabilities: 'search, explore data lineage, understand business context.' Sibling tools (get_*, search) reinforce a read-focused…
Attacks that exploit this kind of access
list_schema_fields. It is categorised as a Read tool in the DataHub MCP Server MCP Server, which means it retrieves data without modifying state.
Register the DataHub MCP Server MCP server in PolicyLayer and add a rule for list_schema_fields: 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 DataHub MCP Server. Nothing to install.
list_schema_fields 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_schema_fields 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_schema_fields. 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_schema_fields is provided by the DataHub MCP Server MCP server (shemreader/mcp-server-datahub). 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 →