Get full details of a specific skill. Args: skill_name: Name of the skill to retrieve Returns: Full skill definition as YAML
AI agents call skill_get to retrieve information from Browser-Use MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This is a read-only operation that queries and returns skill definitions without side effects. It fits the Read category: retrieves or queries data with no side effects (get, fetch). The severity is low because skill metadata retrieval poses minimal risk even if misused by an agent.
From the tool's definition Tool name is 'skill_get' and description states it retrieves 'full details of a specific skill' and 'returns full skill definition as YAML'. No modification, deletion, or execution of skills occurs—only retrieval of existing skill metadata.
Documented attack patterns abuse exactly the kind of access skill_get gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Browser-Use MCP Server, and nothing reaches the server without passing your rules. This is the rule we recommend for skill_get:
{
"version": "1",
"default": "deny",
"tools": {
"skill_get": {}
}
}skill_get 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.
Get full details of a specific skill. Args: skill_name: Name of the skill to retrieve Returns: Full skill definition as YAML. It is categorised as a Read tool in the Browser-Use MCP Server MCP Server, which means it retrieves data without modifying state.
Register the Browser-Use MCP Server MCP server in PolicyLayer and add a rule for skill_get: 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-Use MCP Server. Nothing to install.
skill_get 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 skill_get 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 skill_get. 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.
skill_get is provided by the Browser-Use MCP Server MCP server (saik0s/mcp-browser-use). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Deterministic rules across all 9 Browser-Use MCP Server tools. Per-identity grants. Full audit log. Live in minutes. Nothing to install.
Free to start. No card required.
9 Browser-Use MCP Server tools catalogued and risk-classified — across an index of 42,500+ MCP servers.