filter_generation_context

filter_generation_context

Server RobotWS MCP Server stella555359/robotws_mcp_server
Category Read
Risk class Low
Parameters 00 required

What filter_generation_context does on RobotWS MCP Server

AI agents call filter_generation_context to retrieve information from RobotWS MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.

Why filter_generation_context needs a policy

This tool appears to filter or retrieve test generation context from the indexed metadata stored in SQLite. It performs retrieval and filtering without modifying data or triggering external operations. The empty description lowers confidence slightly, but the contextual evidence from the server's stated purpose and consistent naming patterns of sibling tools strongly suggest read-only metadata access.

From the tool's definition Tool name 'filter_generation_context' combined with server purpose of providing 'generation context to help Cursor's LLM draft testcases' indicates querying/retrieval of stored metadata.

Questions about filter_generation_context

What does the filter_generation_context tool do? +

filter_generation_context. It is categorised as a Read tool in the RobotWS MCP Server MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on filter_generation_context? +

Register the RobotWS MCP Server MCP server in PolicyLayer and add a rule for filter_generation_context: 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 RobotWS MCP Server. Nothing to install.

What risk level is filter_generation_context? +

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

Can I rate-limit filter_generation_context? +

Yes. Add a rate_limit block to the filter_generation_context 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 filter_generation_context completely? +

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

filter_generation_context is provided by the RobotWS MCP Server MCP server (stella555359/robotws_mcp_server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

// THE FULL RECORD

filter_generation_context is one line of RobotWS MCP Server's registry record.

The record carries the whole server: verified identity, auth posture, risk grade, every tool classified, recommended policy — re-checked continuously.

Teams ship this data inside their own products. See what a licence covers →

// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.