Set a comment on a frame for the duration of this session (non-persistent).
AI agents use set_frame_comment to create or update resources in SharkMCP — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your SharkMCP environment.
This tool modifies frame metadata by adding comments, which is a reversible write operation. The non-persistent nature (session-only scope) and the fact that comments are metadata rather than packet data itself keeps severity low. It does not execute code, delete data, or affect financial operations.
From the tool's definition Tool name contains 'set' and description explicitly states 'Set a comment on a frame' - this creates or modifies data. The description clarifies the modification is 'non-persistent' and scoped to 'this session', which limits blast radius.
Documented attack patterns abuse exactly the kind of access set_frame_comment gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and SharkMCP, and nothing reaches the server without passing your rules. This is the rule we recommend for set_frame_comment:
{
"version": "1",
"default": "deny",
"tools": {
"set_frame_comment": {
"limits": [
{
"counter": "set_frame_comment_rate",
"window": "minute",
"max": 30,
"scope": "grant"
}
]
}
}
}set_frame_comment 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.
Set a comment on a frame for the duration of this session (non-persistent). It is categorised as a Write tool in the SharkMCP MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Shark MCP server in PolicyLayer and add a rule for set_frame_comment: 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 SharkMCP. Nothing to install.
set_frame_comment 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_frame_comment 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_frame_comment. 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_frame_comment is provided by the Shark MCP server (weirdmachine64/sharkmcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Deterministic rules across all 30 SharkMCP tools. Per-identity grants. Full audit log. Live in minutes. Nothing to install.
Free to start. No card required.
30 SharkMCP tools catalogued and risk-classified — across an index of 42,500+ MCP servers.