AI agents invoke aat_devqa to trigger actions in AWT (AI Watch Tester). What it does depends on the arguments the agent supplies, and its effects often reach beyond the immediate call — builds kicked off, notifications sent, workflows started.
Given the server context (Playwright-based E2E testing, browser automation), tools on this server generally execute browser actions or run test scripts. The 'devqa' suffix suggests a development QA execution function. However, the empty description lowers confidence significantly.
From the tool's definition Tool name 'aat_devqa' on an AI-powered E2E testing server with sibling tools like aat_run, aat_scan, aat_snapshot suggesting execution of tests/browser actions; description is empty.
Documented attack patterns abuse exactly the kind of access aat_devqa gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and AWT (AI Watch Tester), and nothing reaches the server without passing your rules. This is the rule we recommend for aat_devqa:
{
"version": "1",
"default": "deny",
"tools": {
"aat_devqa": {
"limits": [
{
"counter": "aat_devqa_rate",
"window": "minute",
"max": 10,
"scope": "grant"
}
]
}
}
}aat_devqa stays usable, but rate-capped — a runaway agent can't fire it dozens of times a minute. Everything else on the server is denied unless you say otherwise.
Free to start. No card required.
aat_devqa. It is categorised as a Execute tool in the AWT (AI Watch Tester) MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
Register the AWT (AI Watch Tester) MCP server in PolicyLayer and add a rule for aat_devqa: 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 AWT (AI Watch Tester). Nothing to install.
aat_devqa is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.
Yes. Add a rate_limit block to the aat_devqa 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 aat_devqa. 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.
aat_devqa is provided by the AWT (AI Watch Tester) MCP server (ksgisang/ai-watch-tester). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from AWT (AI Watch Tester), 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.
12 AWT (AI Watch Tester) tools catalogued and risk-classified — across an index of 43,000+ MCP servers.