Provides the partitions for a given Iceberg table
AI agents call get_table_partitions to retrieve information from IcebergMCP without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves metadata about table partitions in an Apache Iceberg data lakehouse. It is purely informational—it queries and returns partition information without creating, modifying, deleting, executing code, or moving money. The sibling tools (get_iceberg_tables, get_namespaces, get_table_properties, get_table_schema) all follow the same read-only pattern.
From the tool's definition The tool name is 'get_table_partitions' and description states it 'Provides the partitions for a given Iceberg table'. The verb 'provides' and the 'get_' prefix indicate data retrieval with no modification or execution of arbitrary operations.
Documented attack patterns abuse exactly the kind of access get_table_partitions gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and IcebergMCP, and nothing reaches the server without passing your rules. This is the rule we recommend for get_table_partitions:
{
"version": "1",
"default": "deny",
"tools": {
"get_table_partitions": {}
}
}get_table_partitions 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.
Provides the partitions for a given Iceberg table. It is categorised as a Read tool in the IcebergMCP MCP Server, which means it retrieves data without modifying state.
Register the Iceberg MCP server in PolicyLayer and add a rule for get_table_partitions: 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 IcebergMCP. Nothing to install.
get_table_partitions 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_table_partitions 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_table_partitions. 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_table_partitions is provided by the Iceberg MCP server (ryft-io/iceberg-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Deterministic rules across all 5 IcebergMCP tools. Per-identity grants. Full audit log. Live in minutes. Nothing to install.
Free to start. No card required.
5 IcebergMCP tools catalogued and risk-classified — across an index of 42,500+ MCP servers.