View all your collaboration sessions with a specific team.
AI agents call view_team_collaboration_history to retrieve information from Automagik Tools without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves and displays existing collaboration session history for a team. It has no side effects, does not modify data, execute code, or trigger external operations. The blast radius of misuse is minimal - an agent could at worst access sensitive collaboration history it shouldn't see, but cannot create, delete, or execute anything. This is a classic Read category tool.
From the tool's definition Tool name contains 'view' and description states 'View all your collaboration sessions' - this is a read-only operation that retrieves historical collaboration data without modifying or executing anything.
Documented attack patterns abuse exactly the kind of access view_team_collaboration_history gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Automagik Tools, and nothing reaches the server without passing your rules. This is the rule we recommend for view_team_collaboration_history:
{
"version": "1",
"default": "deny",
"tools": {
"view_team_collaboration_history": {}
}
}view_team_collaboration_history 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.
View all your collaboration sessions with a specific team. It is categorised as a Read tool in the Automagik Tools MCP Server, which means it retrieves data without modifying state.
Register the Automagik Tools MCP server in PolicyLayer and add a rule for view_team_collaboration_history: 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 Automagik Tools. Nothing to install.
view_team_collaboration_history 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 view_team_collaboration_history 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 view_team_collaboration_history. 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.
view_team_collaboration_history is provided by the Automagik Tools MCP server (namastexlabs/automagik-tools). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from Automagik Tools, 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.
122 Automagik Tools tools catalogued and risk-classified — across an index of 43,000+ MCP servers.