Drafts a short AI use policy for a small business from an eight-question questionnaire, returning the policy as Markdown.
What you can do
Retrieve the eight-question policy questionnaire with its question ids, wording, types and limits
Ask the person for their answers and build a roughly two-page, ten-section AI use policy draft in Markdown
Get a list of parts still to fill in or check, to show alongside the draft
When to use it
Useful when a small business needs a first internal AI use policy covering approved tools, data rules, allowed and prohibited uses, human review and approval of new tools, and wants a starting draft rather than a blank page.
Requirements
A remote MCP endpoint over streamable HTTP; no account, API key or environment variable is declared. The assistant must collect the answers from the person.
Before you install
The draft is for internal use and is not legal advice; the server advises having counsel review it. The tools fill a fixed template and call no AI model, and the server states it does not store or log answers, but the answers still pass through the remote endpoint.
Enable the server for the chats that should use its tools.
Web executable via Streamable HTTP. Remote servers run from the web runtime once configured in a workspace.
Use with an agent
Paste this prompt into Claude Code, Codex, Cursor or another agent — or into SourceWeft chat. The agent reads this server's install guide, shows you its publisher, endpoint and sign-in, and adds it to your client once you agree. Keys never go into a command.
Read https://sourceweft.com/mcp/com.igdigi%2Fai-use-policy/install.md and connect the MCP server it describes to my client. Before changing any config, show me its publisher, endpoint and sign-in method and wait for my OK. Never put an API key in a command or in a file I would commit; ask me where it should come from.
Returns the short questionnaire behind draft_ai_use_policy: eight questions for a small business (company name, industry, AI tools in use, kinds of data the team handles, allowed uses, prohibited uses, who approves new tools, review cadence). Each question has an id, plain wording, type, limits and an example. Call this first, ask the person the questions, then pass their answers to draft_ai_use_policy. Takes no arguments, makes no network calls, stores nothing.
Takes no parameters.
draft_ai_use_policy
Draft a short AI use policy
Builds a short AI use policy draft in Markdown (ten sections, about two pages) from the answers to get_policy_questions: purpose, scope, approved tools, data rules (what never goes into free or unapproved AI tools), allowed and prohibited uses, human review of AI output, approval of new tools, incident reporting and a review date. It is a fixed template filled with the answers: no AI model is called, there is no network access, and this server does not store or log the answers. Only company_name is required. Every other answer left out becomes a bracketed placeholder in the draft, and after the policy the result lists them, together with any free plan or kind of data that needs a second look (show that list to the person). Ask the person for the answers, do not invent them. Optional effective_date (YYYY-MM-DD) defaults to today (UTC). The output is a draft for internal use, not legal advice.
How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.
Reached in the last 30 daysRequired25 pts
Auth declaredRequired10 pts
Tools listedRequired15 pts
DescriptionRequired15 pts
Logo10 pts
Documentation15 pts
Declare a GitHub repository with a README, or serve resource_documentation in the OAuth protected-resource metadata.
LicenseNot applicable
A hosted service is used under its provider's terms, so no license is expected here. This check is left out of the percentage.
