artifacts_set_access
Change an artifact's access level. 'shared' makes the unguessable link the capability (anyone-with-link); 'private' revokes that — the link 404s for anyone not signed into the workspace. Existing shared links keep the same URL when re-shared.
This record as markdown: /tools/io-github-saloprj-dialogbrain/artifacts-set-access.md
What artifacts_set_access does on Dialogbrain
AI agents use artifacts_set_access to create or update resources in Dialogbrain, usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Dialogbrain environment.
| Parameter | Type | Required | Description |
|---|---|---|---|
artifact_id | integer | Yes | The artifact to change. |
access_level | string | Yes | 'shared' (anyone-with-link) or 'private' (in-app only). |
Parameters from the server's own tool schema.
Why artifacts_set_access is rated Medium
This tool modifies access control settings for artifacts reversibly. It changes sharing permissions but does not delete, destroy, or execute arbitrary operations. The effect is reversible: toggling between 'shared' and 'private' states.
From the tool's definition Tool description: 'Change an artifact's access level' — modifies access permissions. 'shared' makes...the link the capability; 'private' revokes that' — reversibly changes sharing state.
Attacks that exploit this kind of access
The rule that runs artifacts_set_access safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Dialogbrain, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For artifacts_set_access, this is the rule to start with:
artifacts_set_access 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.
The button opens the PolicyLayer dashboard: create your workspace, connect Dialogbrain, apply this rule, and every artifacts_set_access call is checked against it from then on.
Questions about artifacts_set_access
Change an artifact's access level. 'shared' makes the unguessable link the capability (anyone-with-link); 'private' revokes that — the link 404s for anyone not signed into the workspace. Existing shared links keep the same URL when re-shared. It is categorised as a Write tool in the Dialogbrain MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
artifacts_set_access accepts 2 parameters: artifact_id, access_level. Required: artifact_id, access_level. The full parameter table on this page comes from the server's own tool schema.
Register the Dialogbrain MCP server in PolicyLayer and add a rule for artifacts_set_access: 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 Dialogbrain. Nothing to install.
artifacts_set_access 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 artifacts_set_access 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 artifacts_set_access. 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.
artifacts_set_access is provided by the Dialogbrain MCP server (https://api.dialogbrain.com/mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Dialogbrain, and thousands of servers like it.
This server
Across the catalogue