Low Risk

get_table_properties

get_table_properties

How to control get_table_properties ↓

AI agents call get_table_properties 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.

Low Risk

This tool retrieves table properties metadata from an Iceberg data lakehouse. The 'get_' prefix and context of querying metadata indicate this is a read-only operation with no side effects. While the tool description is empty, the naming pattern and sibling tools strongly suggest metadata retrieval rather than modification or execution.

From the tool's definition Tool name 'get_table_properties' and sibling tools (get_iceberg_tables, get_namespaces, get_table_partitions, get_table_schema) all use the 'get_' prefix, which is a strong convention for read-only retrieval operations.

Documented attack patterns abuse exactly the kind of access get_table_properties 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_properties:

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

get_table_properties is read-only, so it stays allowed — but everything else on the server is denied unless you say otherwise.

  1. Create a free account and register IcebergMCP — nothing to install.
  2. Add this policy — paste it, or build it visually.
  3. Point your MCP client (Claude, Cursor, anything) at your gateway URL.
CAP THIS TOOL →

Free to start. No card required.

Go deeper

What does the get_table_properties tool do? +

get_table_properties. It is categorised as a Read tool in the IcebergMCP MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on get_table_properties? +

Register the Iceberg MCP server in PolicyLayer and add a rule for get_table_properties: 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.

What risk level is get_table_properties? +

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

Can I rate-limit get_table_properties? +

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

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

get_table_properties 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.

Enforce policy on every IcebergMCP tool call.

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.

// GET IN TOUCH

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

Message sent.

We'll get back to you soon.