AI agents use set_stream_favorite to create or update resources in Packmate — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Packmate environment.
This tool creates or modifies metadata (favorite flag) on a stream in a reversible manner. It is a Write operation because it alters state but does not delete data, execute code, move funds, or trigger external processes. The blast radius is minimal—a misused agent could only toggle favorite flags. Severity is low because the operation is fully reversible and has no destructive, financial, or execution implications.
From the tool's definition Tool description states 'Mark or unmark a stream as favorite' — a reversible state modification operation that changes metadata without affecting underlying data.
Attacks that exploit this kind of access
Mark or unmark a stream as favorite. It is categorised as a Write tool in the Packmate MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Packmate MCP server in PolicyLayer and add a rule for set_stream_favorite: 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 Packmate. Nothing to install.
set_stream_favorite 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 set_stream_favorite 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 set_stream_favorite. 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.
set_stream_favorite is provided by the Packmate MCP server (umbra2728/packmate-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 →