Diagnose Safari support and accessibility. Useful for debugging Safari integration.
AI agents call diagnose_safari_support to retrieve information from Browser History Analysis MCP without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves diagnostic information about Safari support and accessibility. It does not create, modify, delete, or execute external operations—it only queries and reports status information. This aligns with the Read category for tools that retrieve or query data with no side effects. The severity is low because the tool operates on system/browser metadata with minimal blast radius if misused by an agent.
From the tool's definition The tool name contains "diagnose" and the description states it is "useful for debugging Safari integration." It performs diagnostic inspection of Safari support and accessibility status without modifying, executing operations on, or deleting any data.
Documented attack patterns abuse exactly the kind of access diagnose_safari_support gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Browser History Analysis MCP, and nothing reaches the server without passing your rules. This is the rule we recommend for diagnose_safari_support:
{
"version": "1",
"default": "deny",
"tools": {
"diagnose_safari_support": {}
}
}diagnose_safari_support 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.
Diagnose Safari support and accessibility. Useful for debugging Safari integration. It is categorised as a Read tool in the Browser History Analysis MCP MCP Server, which means it retrieves data without modifying state.
Register the Browser History Analysis MCP server in PolicyLayer and add a rule for diagnose_safari_support: 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 Browser History Analysis MCP. Nothing to install.
diagnose_safari_support 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 diagnose_safari_support 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 diagnose_safari_support. 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.
diagnose_safari_support is provided by the Browser History Analysis MCP server (mixophrygian/browser_history_mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from Browser History Analysis MCP, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.
Free to start. No card required.
7 Browser History Analysis MCP tools catalogued and risk-classified — across an index of 43,000+ MCP servers.