unsubscribe_from_object_notifications
Unsubscribe the authenticated account from notifications for a raw Huly object by removing its collaborator row. Idempotent when already absent.
This record as markdown: /tools/io-github-dearlordylord-huly-mcp/unsubscribe-from-object-notifications.md
What unsubscribe_from_object_notifications does on Huly
AI agents use unsubscribe_from_object_notifications to create or update resources in Huly, usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Huly environment.
Why unsubscribe_from_object_notifications is rated Medium
This tool modifies subscription/collaborator state by removing a collaborator row. While it removes data, it is a reversible action (the user can re-subscribe), so it falls under Write rather than Destructive. The blast radius is medium as it affects notification delivery for the authenticated account on a specific object.
From the tool's definition Unsubscribe the authenticated account from notifications for a raw Huly object by removing its collaborator row
Attacks that exploit this kind of access
The rule that runs unsubscribe_from_object_notifications safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Huly, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For unsubscribe_from_object_notifications, this is the rule to start with:
unsubscribe_from_object_notifications 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.
The button opens the PolicyLayer dashboard: create your workspace, connect Huly, apply this rule, and every unsubscribe_from_object_notifications call is checked against it from then on.
Questions about unsubscribe_from_object_notifications
Unsubscribe the authenticated account from notifications for a raw Huly object by removing its collaborator row. Idempotent when already absent. It is categorised as a Write tool in the Huly MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Huly MCP server in PolicyLayer and add a rule for unsubscribe_from_object_notifications: 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 Huly. Nothing to install.
unsubscribe_from_object_notifications 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 unsubscribe_from_object_notifications 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 unsubscribe_from_object_notifications. 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.
unsubscribe_from_object_notifications is provided by the Huly MCP server (@firfi/huly-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Huly, and thousands of servers like it.
This server
Across the catalogue