AI agents use set_title_internal_data to create or update resources in Playfab — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Playfab environment.
This tool creates or modifies server-side title configuration data. It is clearly a Write operation (reversible modification), not Destructive (no deletion indicated). However, it affects server-only internal data which could impact game behavior, authentication, or configuration across all players, warranting high severity.
From the tool's definition Tool name 'set_title_internal_data' and description 'Sets server-only title data' directly indicates data creation/modification. The data is internal/server-only, indicating restricted but modifiable configuration.
Attacks that exploit this kind of access
Sets server-only title data that is not accessible by clients. It is categorised as a Write tool in the Playfab MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Playfab MCP server in PolicyLayer and add a rule for set_title_internal_data: allow, deny, rate-limit, or require approval. Point your MCP client at the PolicyLayer proxy URL and the rule is enforced on every call, before it reaches Playfab. Nothing to install.
set_title_internal_data is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.
Yes. Add a rate_limit block to the set_title_internal_data rule in your PolicyLayer policy. For example, setting max: 10 and window: 60 limits the tool to 10 calls per minute. Rate limits are tracked per agent session and reset automatically.
Set action: deny in the PolicyLayer policy for set_title_internal_data. The AI agent will receive a policy violation error and cannot call the tool. You can also include a reason field to explain why the tool is blocked.
set_title_internal_data is provided by the Playfab MCP server (@akiojin/playfab-mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Every MCP server has a record like this.
Type a name, get the same breakdown: verified identity, auth posture, risk grade, capabilities, recommended policy.
Teams ship this data inside their own products. See what a licence covers →