AI agents use katalon_manage_object_repository to create or update resources in Katalon — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Katalon environment.
Managing an object repository in QA automation typically involves creating, updating, and modifying test object definitions (selectors, properties, metadata). This is a reversible data modification operation (Write category).
From the tool's definition Tool name 'katalon_manage_object_repository' combined with 'Manage object repository' in description indicates create/modify operations on test automation objects. 'Smart healing capabilities' suggests automated corrections or updates to object definitions.
Attacks that exploit this kind of access
Manage object repository with smart healing capabilities. It is categorised as a Write tool in the Katalon MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Katalon MCP server in PolicyLayer and add a rule for katalon_manage_object_repository: 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 Katalon. Nothing to install.
katalon_manage_object_repository is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.
Yes. Add a rate_limit block to the katalon_manage_object_repository 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 katalon_manage_object_repository. 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.
katalon_manage_object_repository is provided by the Katalon MCP server (pareshsoni468/katalon-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 →