Update plugin view component properties.
AI agents use update_plugin_view to create or update resources in HC3 MCP Server — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your HC3 MCP Server environment.
This tool modifies existing plugin view properties, which is a reversible write operation. It does not delete data (not Destructive), execute arbitrary code (not Execute), involve financial transactions (not Financial), or read-only retrieve data (not Read).
From the tool's definition Tool name 'update_plugin_view' and description 'Update plugin view component properties' indicate modification of plugin UI/view configuration.
Attacks that exploit this kind of access
Update plugin view component properties. It is categorised as a Write tool in the HC3 MCP Server MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the HC3 MCP Server MCP server in PolicyLayer and add a rule for update_plugin_view: 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 HC3 MCP Server. Nothing to install.
update_plugin_view 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_plugin_view 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_plugin_view. 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_plugin_view is provided by the HC3 MCP Server MCP server (jangabrielsson/hc3_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 →