meeting_artifact_get
Read one saved meeting transcript (Markdown with speakers and timestamps) by the id returned from meeting_artifacts_list. Long transcripts are returned in pages via offset.
This record as markdown: /tools/cowork-os/meeting-artifact-get.md
What meeting_artifact_get does on CoWork OS
AI agents call meeting_artifact_get to retrieve information from CoWork OS without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
Why meeting_artifact_get is rated Low
Tool retrieves meeting transcripts without side effects or data modification.
From the tool's definition Read one saved meeting transcript by id with offset pagination.
Attacks that exploit this kind of access
The rule that runs meeting_artifact_get safely
PolicyLayer is an MCP gateway: it sits between your AI agents and CoWork OS, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For meeting_artifact_get, this is the rule to start with:
meeting_artifact_get is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.
The button opens the PolicyLayer dashboard: create your workspace, connect CoWork OS, apply this rule, and every meeting_artifact_get call is checked against it from then on.
Questions about meeting_artifact_get
Read one saved meeting transcript (Markdown with speakers and timestamps) by the id returned from meeting_artifacts_list. Long transcripts are returned in pages via offset. It is categorised as a Read tool in the CoWork OS MCP Server, which means it retrieves data without modifying state.
Register the CoWork OS MCP server in PolicyLayer and add a rule for meeting_artifact_get: 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 CoWork OS. Nothing to install.
meeting_artifact_get is a Read tool with low risk. Read-only tools are generally safe to allow by default.
Yes. Add a rate_limit block to the meeting_artifact_get 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 meeting_artifact_get. 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.
meeting_artifact_get is provided by the CoWork OS MCP server (CoWork-OS/CoWork-OS). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on CoWork OS, and thousands of servers like it.
This server
Across the catalogue