# get_space_role

A read tool on the Storyblok MCP Server MCP server.

Agent View of the PolicyLayer registry record for `get_space_role`. HTML page: https://policylayer.com/tools/arjuncodess-storyblok-mcp/get-space-role

## Facts

- Tool: `get_space_role`
- Server: Storyblok MCP Server (`arjuncodess/storyblok-mcp`) — https://policylayer.com/tools/arjuncodess-storyblok-mcp.md
- Homepage: https://github.com/ArjunCodess/storyblok-mcp
- Risk category: Read (Low risk)
- Registry record: grade F, 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": "get_space_role",
    "arguments": {}
  }
}
```

## Why get_space_role is rated Low

This tool retrieves role information without modifying, deleting, or executing operations. It has no blast radius if misused by an agent—the worst outcome is unauthorized reading of role metadata, which is low severity. The confidence is slightly reduced due to empty description, but the naming pattern is unambiguous.

From the tool's own definition: "Tool name 'get_space_role' indicates a retrieval operation that queries role information for a space. The 'get_' prefix is a clear indicator of a read-only query with no side effects."

## Use case

AI agents call get_space_role to retrieve information from Storyblok 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 Storyblok MCP Server:

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

## Other tools on Storyblok MCP Server (114)

- `delete_access_token` — Destructive — https://policylayer.com/tools/arjuncodess-storyblok-mcp/delete-access-token.md
- `delete_asset` — Destructive — https://policylayer.com/tools/arjuncodess-storyblok-mcp/delete-asset.md
- `delete_asset_folder` — Destructive — https://policylayer.com/tools/arjuncodess-storyblok-mcp/delete-asset-folder.md
- `delete_branch` — Destructive — https://policylayer.com/tools/arjuncodess-storyblok-mcp/delete-branch.md
- `delete_component` — Destructive — https://policylayer.com/tools/arjuncodess-storyblok-mcp/delete-component.md
- `delete_component_folder` — Destructive — https://policylayer.com/tools/arjuncodess-storyblok-mcp/delete-component-folder.md
- `delete_datasource` — Destructive — https://policylayer.com/tools/arjuncodess-storyblok-mcp/delete-datasource.md
- `delete_datasource_entry` — Destructive — https://policylayer.com/tools/arjuncodess-storyblok-mcp/delete-datasource-entry.md
- `delete_preset` — Destructive — https://policylayer.com/tools/arjuncodess-storyblok-mcp/delete-preset.md
- `delete_release` — Destructive — https://policylayer.com/tools/arjuncodess-storyblok-mcp/delete-release.md
- `delete_space` — Destructive — https://policylayer.com/tools/arjuncodess-storyblok-mcp/delete-space.md
- `delete_space_role` — Destructive — https://policylayer.com/tools/arjuncodess-storyblok-mcp/delete-space-role.md
- `delete_story` — Destructive — https://policylayer.com/tools/arjuncodess-storyblok-mcp/delete-story.md
- `delete_story_scheduling` — Destructive — https://policylayer.com/tools/arjuncodess-storyblok-mcp/delete-story-scheduling.md
- `delete_tag` — Destructive — https://policylayer.com/tools/arjuncodess-storyblok-mcp/delete-tag.md
- `delete_webhook` — Destructive — https://policylayer.com/tools/arjuncodess-storyblok-mcp/delete-webhook.md
- `delete_workflow` — Destructive — https://policylayer.com/tools/arjuncodess-storyblok-mcp/delete-workflow.md
- `delete_workflow_stage` — Destructive — https://policylayer.com/tools/arjuncodess-storyblok-mcp/delete-workflow-stage.md
- `create_branch_deployment` — Execute — https://policylayer.com/tools/arjuncodess-storyblok-mcp/create-branch-deployment.md
- `deploy_branch` — Execute — https://policylayer.com/tools/arjuncodess-storyblok-mcp/deploy-branch.md
- `backup_space` — Other — https://policylayer.com/tools/arjuncodess-storyblok-mcp/backup-space.md
- `ping` — Other — https://policylayer.com/tools/arjuncodess-storyblok-mcp/ping.md
- `compare_branches` — Read — https://policylayer.com/tools/arjuncodess-storyblok-mcp/compare-branches.md
- `fetch_access_tokens` — Read — https://policylayer.com/tools/arjuncodess-storyblok-mcp/fetch-access-tokens.md
- `fetch_asset_folders` — Read — https://policylayer.com/tools/arjuncodess-storyblok-mcp/fetch-asset-folders.md
- `fetch_assets` — Read — https://policylayer.com/tools/arjuncodess-storyblok-mcp/fetch-assets.md
- `fetch_branch_deployments` — Read — https://policylayer.com/tools/arjuncodess-storyblok-mcp/fetch-branch-deployments.md
- `fetch_branches` — Read — https://policylayer.com/tools/arjuncodess-storyblok-mcp/fetch-branches.md
- `fetch_component_folders` — Read — https://policylayer.com/tools/arjuncodess-storyblok-mcp/fetch-component-folders.md
- `fetch_components` — Read — https://policylayer.com/tools/arjuncodess-storyblok-mcp/fetch-components.md
- …and 84 more: https://policylayer.com/tools/arjuncodess-storyblok-mcp.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=arjuncodess-storyblok-mcp · API: https://policylayer.com/registry/api · Policy library: https://policylayer.com/policies/arjuncodess-storyblok-mcp