Create a Timeplus database in iceberg type to connect to Iceberg
AI agents use connect_to_apache_iceberg to create or update resources in Mcp Timeplus — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Mcp Timeplus environment.
The tool performs a database creation/configuration action, which modifies the Timeplus environment by adding a new database resource. This is a Write operation because it creates new infrastructure that can be subsequently modified or deleted.
From the tool's definition Tool creates a Timeplus database connection to Iceberg ("Create a Timeplus database in iceberg type"), which is a reversible resource creation action.
Documented attack patterns abuse exactly the kind of access connect_to_apache_iceberg gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Mcp Timeplus, and nothing reaches the server without passing your rules. This is the rule we recommend for connect_to_apache_iceberg:
{
"version": "1",
"default": "deny",
"tools": {
"connect_to_apache_iceberg": {
"limits": [
{
"counter": "connect_to_apache_iceberg_rate",
"window": "minute",
"max": 30,
"scope": "grant"
}
]
}
}
}connect_to_apache_iceberg 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.
Free to start. No card required.
Create a Timeplus database in iceberg type to connect to Iceberg. It is categorised as a Write tool in the Mcp Timeplus MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Mcp Timeplus MCP server in PolicyLayer and add a rule for connect_to_apache_iceberg: 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 Mcp Timeplus. Nothing to install.
connect_to_apache_iceberg 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 connect_to_apache_iceberg 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 connect_to_apache_iceberg. 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.
connect_to_apache_iceberg is provided by the Mcp Timeplus MCP server (timeplus-io/mcp-timeplus). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from Mcp Timeplus, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.
Free to start. No card required.
7 Mcp Timeplus tools catalogued and risk-classified — across an index of 43,000+ MCP servers.