Critical Risk →

shillbot_get_attestation

[IN DEVELOPMENT] [READ] Fetch a portable AAS v0 attestation for a Verified Shillbot task. Pass task_pda (on-chain Task PDA, base58 — canonical, derivable from public TaskCreated event) for third-party verification, or task_id (orchestrator Firestore doc id) for first-party callers. Exactly one is...

Part of the Swarm Tips — Aggregated AI Agent Activities server.

shillbot_get_attestation can permanently delete data in Swarm Tips — Aggregated AI Agent Activities, with no limits today. PolicyLayer puts allow, deny, and rate-limit rules on every call. Live in minutes.

SECURE SWARM TIPS — AGGREGATED AI AGENT ACTIVITIES →

Free to start. No card required.

AI agents may call shillbot_get_attestation to permanently remove or destroy resources in Swarm Tips — Aggregated AI Agent Activities. Without a policy, an autonomous agent could delete critical data in a loop with no way to undo the damage. PolicyLayer blocks destructive tools by default and requires explicit human approval before enabling them.

Without a policy, an AI agent could call shillbot_get_attestation in a loop, permanently destroying resources in Swarm Tips — Aggregated AI Agent Activities. There is no undo for destructive operations. PolicyLayer blocks this tool by default and only allows it when a human explicitly approves the action.

Destructive tools permanently remove data. Block by default. Only enable with explicit approval workflows.

policy.json
{
  "version": "1",
  "default": "deny",
  "hide": [
    "shillbot_get_attestation"
  ]
}

See the full Swarm Tips — Aggregated AI Agent Activities policy for all 33 tools.

Get this rule live on your own Swarm Tips — Aggregated AI Agent Activities server in minutes. PolicyLayer enforces it on every call, before it runs.

ENFORCE ON MY SWARM TIPS — AGGREGATED AI AGENT ACTIVITIES →

View all 33 tools →

These attack patterns abuse exactly the kind of access shillbot_get_attestation gives an agent. Each links to the full case and the policy that stops it:

Browse the full MCP Attack Database →

Every attack above starts with a tool call. PolicyLayer checks each one against your policy first, so shillbot_get_attestation only ever does what you allow.

SECURE SWARM TIPS — AGGREGATED AI AGENT ACTIVITIES →

Other destructive tools across the catalogue. The same approach applies to each: deny by default, or require human approval.

What does the shillbot_get_attestation tool do? +

[IN DEVELOPMENT] [READ] Fetch a portable AAS v0 attestation for a Verified Shillbot task. Pass task_pda (on-chain Task PDA, base58 — canonical, derivable from public TaskCreated event) for third-party verification, or task_id (orchestrator Firestore doc id) for first-party callers. Exactly one is required. Optional network: 'mainnet' (default) or 'devnet'. Returns {version, network, program_id, task_pda, task_id, agent, composite_score, score_max, verified_at, verification_hash, content_hash, content_id_hash, switchboard_feed, verifier_instructions}. Re-read the named PDA to verify; MCP does not sign. Capture window: between verify_task and finalize_task — closed accounts return 409 (PERMANENTLY UNAVAILABLE).. It is categorised as a Destructive tool in the Swarm Tips — Aggregated AI Agent Activities MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.

How do I enforce a policy on shillbot_get_attestation? +

Register the Swarm Tips — Aggregated AI Agent Activities MCP server in PolicyLayer and add a rule for shillbot_get_attestation: 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 Swarm Tips — Aggregated AI Agent Activities. Nothing to install.

What risk level is shillbot_get_attestation? +

shillbot_get_attestation is a Destructive tool with critical risk. Critical-risk tools should be blocked by default and only enabled with explicit human approval.

Can I rate-limit shillbot_get_attestation? +

Yes. Add a rate_limit block to the shillbot_get_attestation 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.

How do I block shillbot_get_attestation completely? +

Set action: deny in the PolicyLayer policy for shillbot_get_attestation. 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.

What MCP server provides shillbot_get_attestation? +

shillbot_get_attestation is provided by the Swarm Tips — Aggregated AI Agent Activities MCP server (https://mcp.swarm.tips/mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

Enforce policy on every Swarm Tips — Aggregated AI Agent Activities tool call.

Deterministic rules across all 33 Swarm Tips — Aggregated AI Agent Activities tools. Per-identity grants. Full audit log. Live in minutes. Nothing to install.

Free to start. No card required.

4,600+ MCP servers and 31,000+ tools scanned and risk-classified.

// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.