test_fill_form
A execute tool on the Looking Glass MCP server.
This record as markdown: /tools/io-github-sahib-sawhney-wh-looking-glass-mcp/test-fill-form.md
What test_fill_form does on Looking Glass
AI agents invoke test_fill_form to trigger actions in Looking Glass. What it does depends on the arguments the agent supplies, and its effects often reach beyond the immediate call: builds kicked off, notifications sent, workflows started.
| Parameter | Type | Required | Description |
|---|---|---|---|
fields | array | Yes | Array of form fields to fill |
Parameters from the server's own tool schema.
Why test_fill_form is rated High
Based on the tool name, this likely performs a browser action to fill in form fields, which is an Execute-level operation (browser interaction with side effects). However, the empty description significantly lowers confidence. Given the sibling tools are browser automation tools (browser_click, browser_close, etc.), this fits the Execute category.
From the tool's definition Tool name 'test_fill_form' suggests it fills out a form in a browser context; description is empty and uninformative.
Attacks that exploit this kind of access
The rule that runs test_fill_form safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Looking Glass, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For test_fill_form, this is the rule to start with:
test_fill_form stays usable, but rate-capped: a runaway agent can't fire it dozens of times a minute. Everything else on the server is denied unless you say otherwise.
The button opens the PolicyLayer dashboard: create your workspace, connect Looking Glass, apply this rule, and every test_fill_form call is checked against it from then on.
Questions about test_fill_form
test_fill_form is a execute tool on the Looking Glass MCP server. It is categorised as a Execute tool in the Looking Glass MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
test_fill_form accepts 1 parameter: fields. Required: fields. The full parameter table on this page comes from the server's own tool schema.
Register the Looking Glass MCP server in PolicyLayer and add a rule for test_fill_form: 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 Looking Glass. Nothing to install.
test_fill_form is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.
Yes. Add a rate_limit block to the test_fill_form 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 test_fill_form. 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.
test_fill_form is provided by the Looking Glass MCP server (looking-glass-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Looking Glass, and thousands of servers like it.
Across the catalogue