List meeting recordings from Meeting Assistant. Each recording has a summary, action items, transcript, and brief.
AI agents call get-recordings to retrieve information from Akiflow MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves and queries existing meeting recording data. There are no side effects, no data modification, and no execution of external operations. It is purely informational access, fitting the 'Read' category. Severity is low because unauthorized access to meeting recordings, while potentially sensitive, does not directly enable destructive or financial harm through the tool itself.
From the tool's definition Tool name is 'get-recordings' and description states 'List meeting recordings' — a retrieval operation with no modification.
Documented attack patterns abuse exactly the kind of access get-recordings gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Akiflow MCP Server, and nothing reaches the server without passing your rules. This is the rule we recommend for get-recordings:
{
"version": "1",
"default": "deny",
"tools": {
"get-recordings": {}
}
} get-recordings is read-only, so it stays allowed — but everything else on the server is denied unless you say otherwise.
Free to start. No card required.
List meeting recordings from Meeting Assistant. Each recording has a summary, action items, transcript, and brief. It is categorised as a Read tool in the Akiflow MCP Server MCP Server, which means it retrieves data without modifying state.
Register the Akiflow MCP Server MCP server in PolicyLayer and add a rule for get-recordings: 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 Akiflow MCP Server. Nothing to install.
get-recordings 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 get-recordings 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 get-recordings. 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.
get-recordings is provided by the Akiflow MCP Server MCP server (shrimpwtf/akiflow-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from Akiflow MCP Server, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.
Free to start. No card required.
22 Akiflow MCP Server tools catalogued and risk-classified — across an index of 43,000+ MCP servers.