test_generate_assertions
A other tool on the Looking Glass MCP server.
This record as markdown: /tools/io-github-sahib-sawhney-wh-looking-glass-mcp/test-generate-assertions.md
What test_generate_assertions does on Looking Glass
AI agents call test_generate_assertions as a supporting operation in Looking Glass workflows.
Why test_generate_assertions is rated Low
With no description available, classification is speculative. The name implies generating test assertions, which would likely be a Write or Read operation. Without further context, severity and category confidence are low.
From the tool's definition Tool description is empty and uninformative; the name 'test_generate_assertions' suggests generating test assertions, which is a read/write operation of low impact.
Attacks that exploit this kind of access
The rule that runs test_generate_assertions 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_generate_assertions, this is the rule to start with:
test_generate_assertions gets a rate cap, and 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_generate_assertions call is checked against it from then on.
Questions about test_generate_assertions
test_generate_assertions 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.
Register the Looking Glass MCP server in PolicyLayer and add a rule for test_generate_assertions: 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_generate_assertions is a Other tool with low risk. Read-only tools are generally safe to allow by default.
Yes. Add a rate_limit block to the test_generate_assertions 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_generate_assertions. 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_generate_assertions 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.
This server
Across the catalogue