# sf_express_service_inquiry

Inquire about SF Express service availability, restrictions, and capabilities between locations.

Agent View of the PolicyLayer registry record for `sf_express_service_inquiry`. HTML page: https://policylayer.com/tools/100kgforest-sf-express-mcp-server/sf-express-service-inquiry

## Facts

- Tool: `sf_express_service_inquiry`
- Server: SF Express MCP Server (`100kgforest/sf-express-mcp-server`) — https://policylayer.com/tools/100kgforest-sf-express-mcp-server.md
- Homepage: https://github.com/100kgforest/sf-express-mcp-server
- Risk category: Read (Low risk)
- Registry record: grade B, 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": "sf_express_service_inquiry",
    "arguments": {}
  }
}
```

## Why sf_express_service_inquiry is rated Low

This tool retrieves read-only information about SF Express service availability and capabilities between locations. It has no side effects on orders, shipments, or data state. The action is a simple information lookup, classifying it as a Read operation with low severity because misuse would only result in retrieval of informational data, not unauthorized transactions or destructive actions.

From the tool's own definition: "Tool name includes 'inquiry' and description states 'Inquire about SF Express service availability, restrictions, and capabilities' — these are query operations that retrieve information about service status and capabilities without modifying any data or…"

## Use case

AI agents call sf_express_service_inquiry to retrieve information from SF Express MCP Server 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 SF Express MCP Server:

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

## Other tools on SF Express MCP Server (4)

- `sf_express_logistics_services` — Read — https://policylayer.com/tools/100kgforest-sf-express-mcp-server/sf-express-logistics-services.md
- `sf_express_query_routes` — Read — https://policylayer.com/tools/100kgforest-sf-express-mcp-server/sf-express-query-routes.md
- `sf_express_track_shipment` — Read — https://policylayer.com/tools/100kgforest-sf-express-mcp-server/sf-express-track-shipment.md
- `sf_express_create_order` — Write — https://policylayer.com/tools/100kgforest-sf-express-mcp-server/sf-express-create-order.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=100kgforest-sf-express-mcp-server · API: https://policylayer.com/registry/api · Policy library: https://policylayer.com/policies/100kgforest-sf-express-mcp-server