What we check
Tool metadata is scanned before each deployment. The following fields are checked:- Name and slug
- Description and tagline (short description)
- Categories and tags
- Input shape and output shape
- Common pitfalls
- Quickstart usage code and install commands (per language)
npm, pnpm, yarn, bun, pip, uv, cargo, go, gem, composer, or docker). Commands outside that list can fail verification because agents may treat them as authoritative install steps.
If any field is flagged, the deployment fails and the UI shows which field failed, why, and how to fix it.
What prompt injection means here
Prompt injection is when natural-language fields contain instructions intended to:- Override AI behavior or system prompts
- Jailbreak or bypass safety restrictions
- Exfiltrate data or hijack downstream tool consumption
Ignore previous instructionsYou are nowSystem prompt:- Hidden instructions inside code blocks
- Jailbreak or bypass-related language
Avoid these patterns
Write safe metadata instead
Keep descriptions factual and neutral. Focus on:- What the tool does
- Integrations and use cases
- How agents should use it
If deployment fails
- Open the deployment details page.
- Open the Verification step.
- Review the flagged fields, reasons, and suggested fixes.
- Use Edit Tool to update the metadata.
- Redeploy.
Safe writing checklist
- Describe product behavior, capabilities, and integration points.
- Avoid telling the reading AI what to do or ignore.
- Keep content plain, specific, and free of hidden instructions.
- Remove roleplay, jailbreak language, and system-prompt framing.