AI agents use create_pet to create or update resources in MCPet — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your MCPet environment.
This tool creates a new virtual pet entity, which is a reversible Write operation. It does not execute arbitrary code, delete data, move money, or trigger destructive external actions. The blast radius of misuse is minimal—an AI agent could create many pet objects, but this is easily cleaned up and has no financial, security, or critical system impact.
From the tool's definition Tool name 'create_pet' and description 'Create a new virtual pet' indicate data creation with no side effects or irreversible consequences.
Documented attack patterns abuse exactly the kind of access create_pet gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and MCPet, and nothing reaches the server without passing your rules. This is the rule we recommend for create_pet:
{
"version": "1",
"default": "deny",
"tools": {
"create_pet": {
"limits": [
{
"counter": "create_pet_rate",
"window": "minute",
"max": 30,
"scope": "grant"
}
]
}
}
}create_pet stays usable, but capped — an agent stuck in a loop can't make hundreds of changes a minute. Everything else on the server is denied unless you say otherwise.
Free to start. No card required.
Create a new virtual pet. It is categorised as a Write tool in the MCPet MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the MCPet MCP server in PolicyLayer and add a rule for create_pet: 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 MCPet. Nothing to install.
create_pet 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 create_pet 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 create_pet. 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.
create_pet is provided by the MCPet MCP server (shreyaskarnik/mcpet). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from MCPet, 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.
6 MCPet tools catalogued and risk-classified — across an index of 43,000+ MCP servers.