检查浏览器兼容性和特性支持
AI agents call check_browser_compatibility to retrieve information from GSAP MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool performs a read-only operation: it queries and returns information about browser compatibility and feature support. There are no side effects, no data modification, no code execution, and no destructive operations. It aligns with the Read category pattern of retrieving or querying data for informational purposes.
From the tool's definition Tool description states 'check_browser_compatibility' which checks browser compatibility and feature support - a query/lookup operation that retrieves information about browser capabilities without modifying state.
Attacks that exploit this kind of access
检查浏览器兼容性和特性支持. It is categorised as a Read tool in the GSAP MCP Server MCP Server, which means it retrieves data without modifying state.
Register the GSAP MCP Server MCP server in PolicyLayer and add a rule for check_browser_compatibility: 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 GSAP MCP Server. Nothing to install.
check_browser_compatibility 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 check_browser_compatibility 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 check_browser_compatibility. 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.
check_browser_compatibility is provided by the GSAP MCP Server MCP server (lillard01/gsap-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 →