AI agents call validate_tuskr_setup to retrieve information from Tuskr without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
The tool performs configuration validation and inspection only. It queries the state of environment variables, project mappings, and field definitions without altering them. This is a diagnostic/read operation with minimal blast radius — it cannot create, modify, delete, or execute external code. Even if misused by an AI agent, it only retrieves information about the setup.
From the tool's definition Tool description states it 'Check[s] env, project mapping, AutoGen test-case type, and custom fields' — these are read-only validation and inspection operations with no mention of modification, deletion, or execution of external systems.
Attacks that exploit this kind of access
Check env, project mapping, AutoGen test-case type, and custom fields for an app. It is categorised as a Read tool in the Tuskr MCP Server, which means it retrieves data without modifying state.
Register the Tuskr MCP server in PolicyLayer and add a rule for validate_tuskr_setup: 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 Tuskr. Nothing to install.
validate_tuskr_setup 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 validate_tuskr_setup 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 validate_tuskr_setup. 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.
validate_tuskr_setup is provided by the Tuskr MCP server (zapkid/tuskr-mcp). 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 →