AI agents call get_preference to retrieve information from SharkMCP without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves configuration preferences from Wireshark's dissector settings. It performs no creation, modification, deletion, or execution of code. The blast radius of misuse is minimal—at worst, an agent would read preference values that are already configuration data. This is a straightforward read/query operation with no destructive or side-effecting capabilities.
From the tool's definition Tool name is 'get_preference' and description states 'Read one or all sharkd dissector preferences.' The verb 'Read' and lack of any modification or side effects clearly indicates this is a retrieval operation.
Documented attack patterns abuse exactly the kind of access get_preference 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 get_preference:
{
"version": "1",
"default": "deny",
"tools": {
"get_preference": {}
}
}get_preference is read-only, so it stays allowed — but everything else on the server is denied unless you say otherwise.
Free to start. No card required.
Read one or all sharkd dissector preferences. It is categorised as a Read tool in the SharkMCP MCP Server, which means it retrieves data without modifying state.
Register the Shark MCP server in PolicyLayer and add a rule for get_preference: 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.
get_preference is a Read tool with low risk. Read-only tools are generally safe to allow by default.
Yes. Add a rate_limit block to the get_preference 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 get_preference. 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.
get_preference 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.