# url_changed

A read tool on the 1cent MCP server.

Agent View of the PolicyLayer registry record for `url_changed`. HTML page: https://policylayer.com/tools/1cent/url-changed

## Facts

- Tool: `url_changed`
- Server: 1cent (`maxzoa/1cent`) — https://policylayer.com/tools/1cent.md
- Homepage: https://github.com/maxzoa/1cent
- Risk category: Read (Low risk)
- Registry record: grade C, identity unverified
- Server rate-limited: no
- Parameters: 0
- Recommended policy verdict: Allowed

## Example call (MCP tools/call, JSON-RPC 2.0)

```json
{
  "jsonrpc": "2.0",
  "id": 1,
  "method": "tools/call",
  "params": {
    "name": "url_changed",
    "arguments": {}
  }
}
```

## Why url_changed is rated Low

Based on naming convention and sibling tools (all appear to be read-only URL intelligence queries), this tool likely retrieves change history or status information about URLs. The lack of description lowers confidence slightly, but the 'url_*' pattern and integration with a passive intelligence service suggests no side effects, making it a Read operation.

From the tool's own definition: "Tool name 'url_changed' suggests checking or retrieving change status of a URL. No description provided, but the context (URL intelligence service alongside tools like 'url_pulse', 'url_passport', 'demo_url_pulse') indicates it queries URL metadata rather…"

## Use case

AI agents call url_changed to retrieve information from 1cent without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.

## Recommended policy (PolicyLayer)

Verdict: **Allowed**. Enforced by the PolicyLayer MCP gateway (https://policylayer.com/mcp-gateway) before a call reaches 1cent:

```json
{
  "version": "1",
  "default": "deny",
  "tools": {
    "url_changed": {}
  }
}
```

## Other tools on 1cent (8)

- `batch_url_status` — Read — https://policylayer.com/tools/1cent/batch-url-status.md
- `buyer_bridge_status` — Read — https://policylayer.com/tools/1cent/buyer-bridge-status.md
- `catalog_search` — Read — https://policylayer.com/tools/1cent/catalog-search.md
- `demo_live_url_pulse` — Read — https://policylayer.com/tools/1cent/demo-live-url-pulse.md
- `demo_url_pulse` — Read — https://policylayer.com/tools/1cent/demo-url-pulse.md
- `url_extract` — Read — https://policylayer.com/tools/1cent/url-extract.md
- `url_passport` — Read — https://policylayer.com/tools/1cent/url-passport.md
- `url_pulse` — Read — https://policylayer.com/tools/1cent/url-pulse.md

## For agents

This record is a snapshot. Live verdicts and the full registry:

- Check every server in your MCP config at once: `npx -y policylayer stack`
- Vet a server before you add it: install the mcp-precheck skill — `npx skills add https://policylayer.com` (skill text: https://policylayer.com/skill.md)
- Query the registry over MCP: endpoint `https://api.policylayer.com/mcp` — tools `check_mcp_server`, `check_mcp_stack`, `check_tool`, `search_registry`, `get_change_events`

---

Source: the PolicyLayer MCP registry — one continuously verified record per MCP server. Full record: https://policylayer.com/registry?q=1cent · API: https://policylayer.com/registry/api · Policy library: https://policylayer.com/policies/1cent