Get all registered userscripts
AI agents call extension_tool_userscripts_get_all to retrieve information from WebMCP without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool queries and returns information about registered userscripts without modifying, executing, or deleting any data. It is a straightforward read operation that retrieves existing state. The blast radius of misuse is minimal — an AI agent could learn about available userscripts but cannot directly execute them or modify configuration through this tool alone.
From the tool's definition Tool name contains 'get_all' and description states 'Get all registered userscripts' — a retrieval operation with no side effects.
Risk signalsBulk/mass operation — affects multiple targets
Documented attack patterns abuse exactly the kind of access extension_tool_userscripts_get_all gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and WebMCP, and nothing reaches the server without passing your rules. This is the rule we recommend for extension_tool_userscripts_get_all:
{
"version": "1",
"default": "deny",
"tools": {
"extension_tool_userscripts_get_all": {}
}
} extension_tool_userscripts_get_all 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 all registered userscripts. It is categorised as a Read tool in the WebMCP MCP Server, which means it retrieves data without modifying state.
Register the Web MCP server in PolicyLayer and add a rule for extension_tool_userscripts_get_all: 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 WebMCP. Nothing to install.
extension_tool_userscripts_get_all 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 extension_tool_userscripts_get_all 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 extension_tool_userscripts_get_all. 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.
extension_tool_userscripts_get_all is provided by the Web MCP server (miguelspizza/webmcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from WebMCP, 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.
13 WebMCP tools catalogued and risk-classified — across an index of 43,000+ MCP servers.