Automate browser based workflows with AI
Python aiapiautomationbrowserbrowser-automationcomputergptllmplaywrightpowerautomatepuppeteerpythonrpaseleniumvisionworkflow
Document MCP privacy for directory review (#5651)
Marc Kelechava91d967f5d73e
diff --git a/docs/integrations/mcp.mdx b/docs/integrations/mcp.mdxindex 363421246..936d85378 100644--- a/docs/integrations/mcp.mdx+++ b/docs/integrations/mcp.mdx@@ -520,6 +520,14 @@ For localhost testing, start your local Skyvern backend and frontend. You do notThe `/qa` skill uses `skyvern_evaluate` for fast DOM assertions (~10ms each) and `skyvern_act` for natural-language interactions. Tests are generated fresh from each diff, so there are no test files to maintain.</Tip>+## Privacy and data handling++Skyvern MCP follows Skyvern's [Privacy Policy](https://app.termly.io/policy-viewer/policy.html?policyUUID=1d7aaa1b-5565-415a-8984-7146d254f738).++When you use MCP, Skyvern processes the information needed to run the automations you request. This can include prompts, URLs, page content, screenshots, uploaded or downloaded files, workflow definitions, browser/session artifacts, and credentials you explicitly connect through Skyvern. Skyvern may store workflows, run history, artifacts, credentials, and browser/session state as needed to provide the service and support repeatable automations.++Only connect accounts, credentials, and websites that you are authorized to automate.+## Troubleshooting<Accordion title="Invalid API key or 401 errors">diff --git a/tests/unit/test_mcp_tool_titles.py b/tests/unit/test_mcp_tool_titles.pyindex 7d572757e..6564d178d 100644--- a/tests/unit/test_mcp_tool_titles.py+++ b/tests/unit/test_mcp_tool_titles.py@@ -21,6 +21,15 @@ async def test_every_tool_has_a_title() -> None:assert not missing, f"Tools missing title annotation: {missing}"+async def test_every_tool_has_read_only_hint() -> None:+ tools = await mcp.list_tools()+ assert tools, "MCP server registered zero tools"++ missing = [t.name for t in tools if t.annotations is None or t.annotations.readOnlyHint is None]+ assert not missing, f"Tools missing readOnlyHint annotation: {missing}"++@pytest.mark.asyncioasync def test_destructive_tools_flagged() -> None:"""Tools that delete / close / cancel must carry destructiveHint=True."""