AI agents call share_document as a supporting operation in Automagik Tools workflows.
The description is empty, so classification relies solely on the tool name. 'share_document' could imply a Write or Read operation (sharing/sending a document), but without further context it's unclear whether it reads, writes, or executes. Given the ambiguity and empty description, confidence is low. Assigning 'Other' with medium severity as a precaution since document sharing could expose sensitive data.
From the tool's definition Tool name is 'share_document'; description is empty or uninformative.
Documented attack patterns abuse exactly the kind of access share_document 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 share_document:
{
"version": "1",
"default": "deny",
"tools": {
"share_document": {
"limits": [
{
"counter": "share_document_rate",
"window": "minute",
"max": 60,
"scope": "grant"
}
]
}
}
}share_document gets a rate cap, and everything else on the server is denied unless you say otherwise.
Free to start. No card required.
share_document. It is categorised as a Other tool in the Automagik Tools MCP Server, which means it performs auxiliary operations.
Register the Automagik Tools MCP server in PolicyLayer and add a rule for share_document: 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.
share_document is a Other tool with low risk. Read-only tools are generally safe to allow by default.
Yes. Add a rate_limit block to the share_document 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 share_document. 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.
share_document 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.