test_assert

A other tool on the Looking Glass MCP server.

SERVERLooking Glass SOURCElooking-glass-mcp

Low RISK CLASS

Category Other

Parameters 41 required

Recommended Rate-limitedsee the rule below

Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/io-github-sahib-sawhney-wh-looking-glass-mcp/test-assert.md

WHAT IT DOES

What test_assert does on Looking Glass

AI agents call test_assert as a supporting operation in Looking Glass workflows.

Parameter	Type	Required	Description
`type`	string	Yes	Assertion type
`expected`	string \| number	—	Expected value
`selector`	string	—	CSS selector
`attribute`	string	—	Attribute name (for hasAttribute)

Parameters from the server's own tool schema.

RISK

Why test_assert is rated Low

The name suggests a test assertion operation (verifying conditions), which is typically a read/check operation with no side effects. However, the description is empty, lowering confidence significantly. In a browser automation context it likely checks a condition without modifying state, so 'Other' or 'Read' could apply, but with very low confidence due to lack of description.

From the tool's definition Tool name is 'test_assert' and description is empty or uninformative.

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs test_assert 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_assert, this is the rule to start with:

test_assert Rate-limited

test_assert gets a rate cap, and everything else on the server is denied unless you say otherwise.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "test_assert": {
      "limits": [
        {
          "counter": "test_assert_rate",
          "window": "minute",
          "max": 60,
          "scope": "grant"
        }
      ]
    }
  }
}

SET A RULE FOR THIS TOOL → Instant setup, no code required.

The button opens the PolicyLayer dashboard: create your workspace, connect Looking Glass, apply this rule, and every test_assert call is checked against it from then on.

FAQ

Questions about test_assert

What does the test_assert tool do? +

test_assert is a other tool on the Looking Glass MCP server. It is categorised as a Other tool in the Looking Glass MCP Server, which means it performs auxiliary operations.

What parameters does test_assert accept? +

test_assert accepts 4 parameters: type, expected, selector, attribute. Required: type. The full parameter table on this page comes from the server's own tool schema.

How do I enforce a policy on test_assert? +

Register the Looking Glass MCP server in PolicyLayer and add a rule for test_assert: 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.

What risk level is test_assert? +

test_assert is a Other tool with low risk. Read-only tools are generally safe to allow by default.

Can I rate-limit test_assert? +

Yes. Add a rate_limit block to the test_assert 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.

How do I block test_assert completely? +

Set action: deny in the PolicyLayer policy for test_assert. 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.

What MCP server provides test_assert? +

test_assert 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.

KEEP EXPLORING

More on Looking Glass, and thousands of servers like it.

This server

All 71 Looking Glass tools →

Across the catalogue

The MCP Attack Database →

Guides

Roll out MCP under one policy →Tool risk categories →MCP tool →