AI agents use update_paragraph to create or update resources in Zeppelin — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Zeppelin environment.
This tool creates or modifies data reversibly by updating paragraph content in Apache Zeppelin notebooks. While the modification could affect notebook logic and computations, it does not irreversibly delete data (which would be Destructive) or execute arbitrary code (which would be Execute).
From the tool's definition Tool name 'update_paragraph' and description 'Update a paragraph' indicate modification of existing notebook content. Within Zeppelin's notebook management context, this modifies but does not delete data.
Attacks that exploit this kind of access
Update a paragraph. It is categorised as a Write tool in the Zeppelin MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Zeppelin MCP server in PolicyLayer and add a rule for update_paragraph: 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 Zeppelin. Nothing to install.
update_paragraph 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 update_paragraph 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 update_paragraph. 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.
update_paragraph is provided by the Zeppelin MCP server (mihneamanolache/zeppelin-mcp). 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 →