get_grain_policy
Read the content-grain (wisdom-layer) publish policy for the current company. For each content grain it returns whether an agent may publish that grain autonomously (gate_mode 'autonomous') or must route to a human (gate_mode 'human_pre_gate'), plus curate_only and source_corpus_ref. Use this to ...
This record as markdown: /tools/com-getfreedomos-freedom-mcp/get-grain-policy.md
What get_grain_policy does on Freedom Mcp
AI agents call get_grain_policy to retrieve information from Freedom Mcp without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
| Parameter | Type | Required | Description |
|---|---|---|---|
companyId | string | Yes | FreedomOS company id to act within (you must be a member). Required for company-scoped tools. |
Parameters from the server's own tool schema.
Why get_grain_policy is rated Low
This tool retrieves and queries policy configuration data about content publishing gates for the current company. It has no side effects, does not modify data, does not execute external operations, and does not involve financial transactions or destructive actions. It is a straightforward read operation that returns policy metadata to inform decision-making.
From the tool's definition Tool name contains 'get_' and description states 'Read the content-grain...publish policy' and 'returns whether an agent may publish...Use this to understand' — purely informational retrieval with no modifications, side effects, or execution.
Attacks that exploit this kind of access
The rule that runs get_grain_policy safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Freedom Mcp, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For get_grain_policy, this is the rule to start with:
get_grain_policy 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 Freedom Mcp, apply this rule, and every get_grain_policy call is checked against it from then on.
Questions about get_grain_policy
Read the content-grain (wisdom-layer) publish policy for the current company. For each content grain it returns whether an agent may publish that grain autonomously (gate_mode 'autonomous') or must route to a human (gate_mode 'human_pre_gate'), plus curate_only and source_corpus_ref. Use this to understand which content you may publish on your own vs. send for human pre-approval. It is categorised as a Read tool in the Freedom Mcp MCP Server, which means it retrieves data without modifying state.
get_grain_policy accepts 1 parameter: companyId. Required: companyId. The full parameter table on this page comes from the server's own tool schema.
Register the Freedom MCP server in PolicyLayer and add a rule for get_grain_policy: 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 Freedom Mcp. Nothing to install.
get_grain_policy 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_grain_policy 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_grain_policy. 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_grain_policy is provided by the Freedom MCP server (https://twuluxmoognlwtmaoqgo.supabase.co/functions/v1/freedom-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Freedom, and thousands of servers like it.
This server
Across the catalogue