Get test execution results filtered by specific table ID. Returns filtered test execution summary with only test cases for the specified table. Supports pagination (page/offset/size) for efficient data retrieval. Use openl_start_project_tests() first to start test execution.
AI agents call get_test_results_by_table to retrieve information from Openl without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool only reads and retrieves existing test execution data filtered by table ID. It performs no mutations, deletions, or side effects—purely a data retrieval operation with pagination support. The terms 'Get' and 'Returns' confirm read-only semantics. Even in an OpenL rules management context, retrieving test results is a non-destructive, informational action with minimal blast radius.
From the tool's definition Tool retrieves test execution results with filtering and pagination capabilities. Description explicitly states it 'Returns filtered test execution summary' and 'Get test execution results', indicating a query/retrieval operation with no modification.
Attacks that exploit this kind of access
Get test execution results filtered by specific table ID. Returns filtered test execution summary with only test cases for the specified table. Supports pagination (page/offset/size) for efficient data retrieval. Use openl_start_project_tests() first to start test execution. It is categorised as a Read tool in the Openl MCP Server, which means it retrieves data without modifying state.
Register the Openl MCP server in PolicyLayer and add a rule for get_test_results_by_table: 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 Openl. Nothing to install.
get_test_results_by_table 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 get_test_results_by_table 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 get_test_results_by_table. 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.
get_test_results_by_table is provided by the Openl MCP server (openl-mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Every MCP server has a record like this.
Type a name, get the same breakdown: verified identity, auth posture, risk grade, capabilities, recommended policy.
Teams ship this data inside their own products. See what a licence covers →