AI agents use create_disclosure to create or update resources in Satsignal — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Satsignal environment.
This is a Write operation because it creates new derived content (redacted disclosures) from existing data. It does not execute code or trigger external blockchain operations directly, nor does it delete/destroy data. However, the incomplete description ('Produce an audience-specific redacted disclosure from an') limits full confidence.
From the tool's definition Tool description states 'Produce an audience-specific redacted disclosure' - this creates new data (a redacted disclosure document) and modifies/derives information from existing anchored content for different audiences.
Attacks that exploit this kind of access
Produce an audience-specific redacted disclosure from an. It is categorised as a Write tool in the Satsignal MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Satsignal MCP server in PolicyLayer and add a rule for create_disclosure: 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 Satsignal. Nothing to install.
create_disclosure 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_disclosure 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_disclosure. 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_disclosure is provided by the Satsignal MCP server (steleet/satsignal-mcp). 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 →