# perception_embed

[Sub-phase 4.2 — NOT YET IMPLEMENTED] Will generate Clay v1.5 embeddings.

Agent View of the PolicyLayer registry record for `perception_embed`. HTML page: https://policylayer.com/tools/com-geiant-mcp-agentcore/perception-embed

## Facts

- Tool: `perception_embed`
- Server: Mcp Agentcore (`https://packagesmcp-perception-production.up.railway.app/mcp`) — https://policylayer.com/tools/com-geiant-mcp-agentcore.md
- Homepage: https://github.com/GNS-Foundation/geiant
- Risk category: Other (Low risk)
- Registry record: grade D, identity unverified
- Server auth posture: open
- Server rate-limited: no
- Parameters: 1 (1 required)
- Recommended policy verdict: Rate-limited

## Parameters

| Parameter | Type | Required | Description |
| --- | --- | --- | --- |
| `tile_id` | string | yes | tile_id from perception_fetch_tile result |

Parameters from the server's own tool schema.

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

```json
{
  "jsonrpc": "2.0",
  "id": 1,
  "method": "tools/call",
  "params": {
    "name": "perception_embed",
    "arguments": {
      "tile_id": "<tile_id>"
    }
  }
}
```

## Why perception_embed is rated Low

The tool is explicitly marked as not yet implemented, meaning it performs no actual operations. When implemented, generating embeddings would likely be a Read or Execute operation (processing data to produce vector representations), but as it does nothing currently, 'Other' is most appropriate. Confidence is reduced due to the uninformative stub description.

From the tool's own definition: "[Sub-phase 4.2 — NOT YET IMPLEMENTED] Will generate Clay v1.5 embeddings."

## Use case

AI agents call perception_embed as a supporting operation in Mcp Agentcore workflows.

## Recommended policy (PolicyLayer)

Verdict: **Rate-limited**. Enforced by the PolicyLayer MCP gateway (https://policylayer.com/mcp-gateway) before a call reaches Mcp Agentcore:

```json
{
  "version": "1",
  "default": "deny",
  "tools": {
    "perception_embed": {
      "limits": [
        {
          "counter": "perception_embed_rate",
          "window": "minute",
          "max": 60,
          "scope": "grant"
        }
      ]
    }
  }
}
```

## Other tools on Mcp Agentcore (7)

- `perception_classify` — Execute — https://policylayer.com/tools/com-geiant-mcp-agentcore/perception-classify.md
- `gns_get_compliance_report` — Read — https://policylayer.com/tools/com-geiant-mcp-agentcore/gns-get-compliance-report.md
- `gns_get_trust_score` — Read — https://policylayer.com/tools/com-geiant-mcp-agentcore/gns-get-trust-score.md
- `gns_verify_chain` — Read — https://policylayer.com/tools/com-geiant-mcp-agentcore/gns-verify-chain.md
- `perception_fetch_tile` — Read — https://policylayer.com/tools/com-geiant-mcp-agentcore/perception-fetch-tile.md
- `gns_roll_epoch` — Write — https://policylayer.com/tools/com-geiant-mcp-agentcore/gns-roll-epoch.md
- `perception_weather` — Write — https://policylayer.com/tools/com-geiant-mcp-agentcore/perception-weather.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=com-geiant-mcp-agentcore · API: https://policylayer.com/registry/api · Policy library: https://policylayer.com/policies/com-geiant-mcp-agentcore