AI agents call submit_ai_selector as a supporting operation in OpenTester workflows.
With no description available, the function of this tool is ambiguous. The name 'submit_ai_selector' could imply a Write action (submitting a selector configuration) or an Execute action (triggering AI-based selection logic), but without evidence, confidence is very low. Defaulting to Other given the lack of information, while noting medium severity due to the Execute/Write potential in a testing execution context.
From the tool's definition Tool name is 'submit_ai_selector' but description is empty and uninformative.
Documented attack patterns abuse exactly the kind of access submit_ai_selector gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and OpenTester, and nothing reaches the server without passing your rules. This is the rule we recommend for submit_ai_selector:
{
"version": "1",
"default": "deny",
"tools": {
"submit_ai_selector": {
"limits": [
{
"counter": "submit_ai_selector_rate",
"window": "minute",
"max": 60,
"scope": "grant"
}
]
}
}
}submit_ai_selector gets a rate cap, and everything else on the server is denied unless you say otherwise.
Free to start. No card required.
submit_ai_selector. It is categorised as a Other tool in the OpenTester MCP Server, which means it performs auxiliary operations.
Register the OpenTester MCP server in PolicyLayer and add a rule for submit_ai_selector: 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 OpenTester. Nothing to install.
submit_ai_selector 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 submit_ai_selector 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 submit_ai_selector. 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.
submit_ai_selector is provided by the OpenTester MCP server (kznr02/opentester). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from OpenTester, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.
Free to start. No card required.
23 OpenTester tools catalogued and risk-classified — across an index of 43,000+ MCP servers.