# store_credential

A write tool on the MCP Framework Personal MCP server.

Agent View of the PolicyLayer registry record for `store_credential`. HTML page: https://policylayer.com/tools/inggerman-mcps/store-credential

## Facts

- Tool: `store_credential`
- Server: MCP Framework Personal (`inggerman/mcps`) — https://policylayer.com/tools/inggerman-mcps.md
- Homepage: https://github.com/inggerman/mcps
- Risk category: Write (Medium risk)
- Registry record: grade F, identity unverified
- Server rate-limited: no
- Parameters: 0
- Recommended policy verdict: Rate-limited

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

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

## Why store_credential is rated Medium

The name 'store_credential' strongly implies writing/storing sensitive authentication data (credentials) to some storage. Storing credentials carries high severity due to potential security implications if misused. However, the empty description lowers confidence, as the exact behavior is unknown. Classified as Write rather than Execute since 'store' implies persisting data rather than triggering external operations.

From the tool's own definition: "Tool name 'store_credential' — description is empty and uninformative."

## Use case

AI agents use store_credential to create or update resources in MCP Framework Personal, usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your MCP Framework Personal environment.

## Recommended policy (PolicyLayer)

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

```json
{
  "version": "1",
  "default": "deny",
  "tools": {
    "store_credential": {
      "limits": [
        {
          "counter": "store_credential_rate",
          "window": "minute",
          "max": 30,
          "scope": "grant"
        }
      ]
    }
  }
}
```

## Other tools on MCP Framework Personal (911)

- `agent_delete_task` — Destructive — https://policylayer.com/tools/inggerman-mcps/agent-delete-task.md
- `clear_routing_history` — Destructive — https://policylayer.com/tools/inggerman-mcps/clear-routing-history.md
- `consumer_group_delete` — Destructive — https://policylayer.com/tools/inggerman-mcps/consumer-group-delete.md
- `delete_collection` — Destructive — https://policylayer.com/tools/inggerman-mcps/delete-collection.md
- `delete_document` — Destructive — https://policylayer.com/tools/inggerman-mcps/delete-document.md
- `delete_key` — Destructive — https://policylayer.com/tools/inggerman-mcps/delete-key.md
- `delete_tag` — Destructive — https://policylayer.com/tools/inggerman-mcps/delete-tag.md
- `delete_topic` — Destructive — https://policylayer.com/tools/inggerman-mcps/delete-topic.md
- `drop_columns` — Destructive — https://policylayer.com/tools/inggerman-mcps/drop-columns.md
- `drop_duplicates` — Destructive — https://policylayer.com/tools/inggerman-mcps/drop-duplicates.md
- `filesystem_delete` — Destructive — https://policylayer.com/tools/inggerman-mcps/filesystem-delete.md
- `git_branch_delete` — Destructive — https://policylayer.com/tools/inggerman-mcps/git-branch-delete.md
- `git_push` — Destructive — https://policylayer.com/tools/inggerman-mcps/git-push.md
- `git_reset` — Destructive — https://policylayer.com/tools/inggerman-mcps/git-reset.md
- `git_stash_drop` — Destructive — https://policylayer.com/tools/inggerman-mcps/git-stash-drop.md
- `git_tag_delete` — Destructive — https://policylayer.com/tools/inggerman-mcps/git-tag-delete.md
- `image_remove` — Destructive — https://policylayer.com/tools/inggerman-mcps/image-remove.md
- `invalidate_files` — Destructive — https://policylayer.com/tools/inggerman-mcps/invalidate-files.md
- `network_remove` — Destructive — https://policylayer.com/tools/inggerman-mcps/network-remove.md
- `personal_clear_category` — Destructive — https://policylayer.com/tools/inggerman-mcps/personal-clear-category.md
- `personal_delete` — Destructive — https://policylayer.com/tools/inggerman-mcps/personal-delete.md
- `sonar_project_delete` — Destructive — https://policylayer.com/tools/inggerman-mcps/sonar-project-delete.md
- `storage_delete_object` — Destructive — https://policylayer.com/tools/inggerman-mcps/storage-delete-object.md
- `tf_destroy` — Destructive — https://policylayer.com/tools/inggerman-mcps/tf-destroy.md
- `track_change` — Destructive — https://policylayer.com/tools/inggerman-mcps/track-change.md
- `volume_remove` — Destructive — https://policylayer.com/tools/inggerman-mcps/volume-remove.md
- `agent_cancel` — Execute — https://policylayer.com/tools/inggerman-mcps/agent-cancel.md
- `agent_run_batch` — Execute — https://policylayer.com/tools/inggerman-mcps/agent-run-batch.md
- `agent_run_local_script` — Execute — https://policylayer.com/tools/inggerman-mcps/agent-run-local-script.md
- `agent_run_with_timeout` — Execute — https://policylayer.com/tools/inggerman-mcps/agent-run-with-timeout.md
- …and 881 more: https://policylayer.com/tools/inggerman-mcps.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=inggerman-mcps · API: https://policylayer.com/registry/api · Policy library: https://policylayer.com/policies/inggerman-mcps