What Poly will not do

The actions agents are refused outright, and why.

What it is

A short, deliberately fixed list of things no agent may do on your behalf — not with a confirmation prompt, not with your encouragement. These are refusals in the platform itself, not instructions in a prompt that could be talked around.

Where to find it

You will notice it when you ask for one of these and are told no. The actions themselves are all available to you directly, in Settings or in the relevant app.

How to use it

Poly and deeds cannot change your data-contribution consent tier. They cannot share a resource with someone, or publish one, because distribution and visibility are yours to decide. They cannot mark something secure or clear that mark, cannot write key material, and cannot delete your Space. Every one of those is a thing you do yourself.

Use cases

Knowing which requests will be refused before you make them. Understanding why an automation cannot quietly widen your exposure.

Gotchas

Separately from these hard refusals, some proposed actions are routed to Confirmations for approval instead of running immediately. That is a different mechanism: a queue, not a refusal.

Related pages

Section index