PolicyForge MCP Server vs Sovereign AI Act MCP

generate_policy

Generate a legal policy (privacy policy, terms of service, cookie policy, refund policy, EULA, or disclaimer) for a business and return its Markdown content plus a hosted URL. Consumes one policy from the account's quota. IMPORTANT: if you are working inside the user's project, call get_disclosure_checklist and scan the codebase FIRST (dependencies, script tags, cookie writes, outbound hosts), then fill the optional fields below from what the code actually does — do not ask the user for facts you can read from source. Only ask for what code cannot tell you: legal company name, contact email, physical address, governing law. For terms_of_service, eula and disclaimer, always ask for governing_law: without it (or a physical address to infer it from) the document contains a marker to fill in. The result lists claims to verify: specific statements about third parties, certifications or deadlines that your inputs did not supply. Show them to the user and fix them with update_policy before publishing. Generation takes 40-60 seconds; if it is not finished within about 45 seconds this returns a job ID instead, and check_generation fetches the result. Never call generate_policy again for the same policy while a job is running.

generate_baa

Generate a HIPAA Business Associate Agreement (BAA) between a covered entity and a vendor that handles Protected Health Information. Built from the clauses required by 45 CFR 164.504(e) and validated clause by clause before it is returned. Use this instead of generate_policy for BAAs — a BAA is a binding two-party contract, not a published policy, so it needs both parties' legal names and addresses and is never hosted at a public URL. Ask the user for the party details, effective date, and governing law: these are negotiated facts you cannot read from source code. Requires a Pro plan. The result is a draft for counsel to review, not executed legal advice. If it is not finished within about 45 seconds this returns a job ID; use check_generation for the result.